{"action":"closed","issue":{"url":"https://api.github.com/repos/websharks/comet-cache/issues/924","repository_url":"https://api.github.com/repos/websharks/comet-cache","labels_url":"https://api.github.com/repos/websharks/comet-cache/issues/924/labels{/name}","comments_url":"https://api.github.com/repos/websharks/comet-cache/issues/924/comments","events_url":"https://api.github.com/repos/websharks/comet-cache/issues/924/events","html_url":"https://github.com/websharks/comet-cache/issues/924","id":295118101,"number":924,"title":"Massive CPU Resources Being Used Auto Cache Engine","user":{"login":"vestaxpdx","id":1933841,"avatar_url":"https://avatars2.githubusercontent.com/u/1933841?v=4","gravatar_id":"","url":"https://api.github.com/users/vestaxpdx","html_url":"https://github.com/vestaxpdx","followers_url":"https://api.github.com/users/vestaxpdx/followers","following_url":"https://api.github.com/users/vestaxpdx/following{/other_user}","gists_url":"https://api.github.com/users/vestaxpdx/gists{/gist_id}","starred_url":"https://api.github.com/users/vestaxpdx/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vestaxpdx/subscriptions","organizations_url":"https://api.github.com/users/vestaxpdx/orgs","repos_url":"https://api.github.com/users/vestaxpdx/repos","events_url":"https://api.github.com/users/vestaxpdx/events{/privacy}","received_events_url":"https://api.github.com/users/vestaxpdx/received_events","type":"User","site_admin":false},"labels":[{"id":67985958,"url":"https://api.github.com/repos/websharks/comet-cache/labels/cannot%20reproduce","name":"cannot reproduce","color":"fbca04","default":false}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":7,"created_at":"2018-02-07T12:23:35Z","updated_at":"2018-02-15T12:50:05Z","closed_at":"2018-02-15T12:50:05Z","author_association":"NONE","body":"Hi\r\n\r\nI have the auto cache engine running on our sites which have up to 5K pages for a couple years.\r\n\r\nDespite having a 1 second delay, our server suddenly seems to be grinding to a halt during these runs.\r\n\r\nThis never used to be the case, is there any known bug about this? Perhaps it is not respecting the delay any more.\r\n\r\nComet Cache Version Pro v170220\r\nWordPress 4.9.4\r\n\r\nStats for just one hour are:\r\n\r\ndomain1:\r\n   8716 hits by comet cache crawler\r\ndomain2:\r\n   7405 hits by comet cache crawler\r\ndomain3:\r\n   2556 hits by comet cache crawler\r\n\r\nThe above created loads of 50.04 42.52 55.01\r\n\r\nWe have a dedicated server with a spec of:\r\n\r\n2x E5-2620V4 - 16 core (L)\r\nRAM : 64 GB RAM DDR4 2133 Mhz \r\nHard Disk : 6 x 240 GB Performance SSD \r\nRAID : RAID 10\r\n\r\nRunning PHP7.0 with PHP OPcache\r\nApache Server MPM: worker \r\n\r\nOur server never really struggled before, but the last couple of weeks every day it is melting a bit and causes sites to slow down dramatically.\r\n\r\nMany thanks,\r\n"}}
{"actor":{"display_login":"raamdev"}}