Task #5869 (closed)
Opened 8 years ago
Closed 8 years ago
Check UpgradeCheck page
| Reported by: | jamoore | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | OMERO-Beta4.3.2 |
| Component: | Deployment | Version: | n.a. |
| Keywords: | n.a. | Cc: | atarkowska, saloynton, jburel |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description (last modified by jmoore)
The version number for UpgradeCheck will need to be bumped.(Done)
Additionally, the checks seem to be taking quite a long time, which is slowing down start times for the clients and the server.
Change History (8)
comment:1 Changed 8 years ago by jmoore
comment:2 Changed 8 years ago by jmoore
Upgraded the registry:
jmoore@necromancer ~ $ psql -h localhost -U postgres feedback
feedback=# select * from registry_version;
id | version
----+------------
1 | Beta-4.2.2
(1 row)
feedback=# select now();
now
-------------------------------
2011-06-27 16:01:30.749654+01
(1 row)
feedback=# update registry_version set version = 'Beta-4.3.0' where id = 1;
UPDATE 1
comment:3 Changed 8 years ago by jmoore
- Description modified (diff)
- Priority changed from major to minor
comment:4 Changed 8 years ago by jmoore
- Milestone changed from OMERO-Beta4.3.1 to OMERO-Beta4.3.2
- Sprint 2011-07-07 (1) deleted
Won't be able to do anything for the check speed at the moment. During 4.3.1, we migrated hudson off of the same system, hopefully that will have helped.
comment:5 Changed 8 years ago by cxallan
- Resolution set to fixed
- Status changed from new to closed
Updated for 4.3.1 and updated the UpgradeCheck page. Closing.
comment:6 Changed 8 years ago by cxallan
- Resolution fixed deleted
- Status changed from closed to reopened
Woops, re-opening to address slowing down of start times.
comment:7 Changed 8 years ago by cxallan
Referencing ticket #3398 has changed sprint.
comment:8 Changed 8 years ago by jmoore
- Resolution set to fixed
- Status changed from reopened to closed
Closing since the bumping was done. #6965 will check the upgrade check speed later.
Looks like during testing (?) there were quite a number of hits:
feedback=# select date, count(*) from ( select date_trunc('day', creation_date) as date from registry_hit where creation_date < '2011-05-16 00:00:00+01' order by id desc limit 100000) x group by date order by date desc; date | count ------------------------+------- 2011-05-15 00:00:00+01 | 14510 2011-05-14 00:00:00+01 | 14793 2011-05-13 00:00:00+01 | 19517 2011-05-12 00:00:00+01 | 36200 2011-05-11 00:00:00+01 | 14980 (5 rows)Or:
feedback=# create table registry_hit_per_day(creation_date timestamp with time zone, count int4); CREATE TABLE feedback=# insert into registry_hit_per_day select date_trunc('day', creation_date), count(*) from registry_hit group by date_trunc('day', creation_date);INSERT 0 1219 feedback=# select creation_date, round((count::float / 24 / 60)::numeric, 2) as "per min" from registry_hit_per_day order by count desc; creation_date | per min ------------------------+--------- 2011-05-11 00:00:00+01 | 32.03 2011-05-12 00:00:00+01 | 25.14 2011-05-06 00:00:00+01 | 20.19 2011-05-23 00:00:00+01 | 14.40 2011-05-13 00:00:00+01 | 13.55 2011-05-10 00:00:00+01 | 11.44 2010-09-07 00:00:00+01 | 11.24 2011-05-05 00:00:00+01 | 11.11 2009-10-15 00:00:00+01 | 10.71 2011-05-14 00:00:00+01 | 10.27 2011-05-15 00:00:00+01 | 10.08