Ticket #604 (closed maintenance: invalid)
Times for admin tasks
| Reported by: | ed | Owned by: | chris |
|---|---|---|---|
| Priority: | minor | Milestone: | Maintenance |
| Component: | Live server | Keywords: | |
| Cc: | Estimated Number of Hours: | 0.0 | |
| Add Hours to Ticket: | 0 | Billable?: | yes |
| Total Hours: | 0.1 |
Description
I am timing some of the admin tasks and keeping a log here for reference. Front of the site is great, backend is still like hauling ghosts through jelly for me.
58 seconds: https://www.transitionnetwork.org/admin/user/user/create
Change History
comment:2 Changed 3 years ago by jim
Ed, can you please note the date/time this happens so we can try to relate the slowness to munin and work I'd been doing (which might have emptied the caches and made it slow temporarily). Thanks!
comment:3 in reply to: ↑ 1 Changed 3 years ago by chris
- Add Hours to Ticket changed from 0.0 to 0.1
- Owner changed from jim to chris
- Total Hours changed from 0.0 to 0.1
- Component changed from Drupal modules & settings to Live server
- Priority changed from major to minor
Replying to ed:
today it took more than 2 mins for this
https://www.transitionnetwork.org/admin/content/node/overview
It just took 13 seconds for me.
58 seconds: https://www.transitionnetwork.org/admin/user/user/create
That took 8 seconds.
I think this has been solved with ticket:593#comment:12 -- Ed can you confirm that this ticket can now be closed?
comment:4 Changed 3 years ago by ed
- Status changed from new to closed
- Resolution set to invalid
trying it now was OK; it seems much slower in the mornings, and I hear from Rob and others at TN tht the first admin task of the day is very slow. But no more work of this nature on TNv2 so closing.
comment:5 follow-up: ↓ 6 Changed 3 years ago by jim
The caches will be cold first thing - so will always be slow as they're rebuilt by the early admin jobs.
comment:6 in reply to: ↑ 5 Changed 3 years ago by chris
Replying to jim:
The caches will be cold first thing
It looks to me that BOA is set to kill the Redis cache at midnight -- I suspect this is the primary cause of this issue and would suggest that this theory could be tested by disabling the wiping of the cache.
comment:7 follow-up: ↓ 8 Changed 3 years ago by ed
it's not a biggie, and i'm happy to let this lie as i wrote above, thanks
comment:8 in reply to: ↑ 7 Changed 3 years ago by chris
Replying to ed:
it's not a biggie, and i'm happy to let this lie as i wrote above, thanks
OK, but please do bear in mind that this is probably a BOA "feature" -- this is the opposite of how Redis is supposed to be run:
Redis is designed to be a very long running process in your server.
comment:9 Changed 3 years ago by chris
It looks like this "feature" should be removed with the BOA upgrade on ticket:707:
is there a reason to restart redis every night?
Posted by omega8cc on December 16, 2013 at 7:30pm:
Next BOA release will... be able to get rid of this reset procedure.
today it took more than 2 mins for this
https://www.transitionnetwork.org/admin/content/node/overview