Task #3179 (closed)
Opened 14 years ago
Closed 13 years ago
[4.3.0] Document the use of omero.db.poolsize
Reported by: | jamoore | Owned by: | jamoore |
---|---|---|---|
Priority: | critical | Milestone: | OMERO-Beta4.3.1 |
Component: | Performance | Version: | n.a. |
Keywords: | n.a. | Cc: | |
Resources: | n.a. | Referenced By: | n.a. |
References: | n.a. | Remaining Time: | 0.0d |
Sprint: | 2011-07-07 (1) |
Description
On ScalingOmero and on the official documentation it should be clear that anyone who has enough power in their postgres install (i.e. 100 simultaneous connections) should not be running with the default 10 connections which OMERO configures via omero.db.poolsize.
Change History (7)
comment:1 Changed 14 years ago by jburel
- Sprint changed from 2010-10-28 (18) to 2010-11-11 (19)
comment:2 Changed 14 years ago by jburel
- Sprint changed from 2010-11-11 (19) to 2020-11-25 (20)
Moved from sprint 2010-11-11 (19)
comment:3 Changed 14 years ago by jmoore
- Milestone changed from OMERO-Beta4.2.1 to OMERO-Beta4.2.2
- Sprint 2020-11-25 (20) deleted
Pushing. May should be documented with the upcoming session concurrency fixes.
comment:4 Changed 13 years ago by jmoore
- Summary changed from [4.2.1] Document the use of omero.db.poolsize to [4.3.0] Document the use of omero.db.poolsize
comment:5 Changed 13 years ago by jmoore
- Milestone changed from OMERO-Beta4.2.2 to OMERO-Beta4.3
comment:6 Changed 13 years ago by jmoore
- Owner set to jmoore
- Remaining Time set to 0.25
- Status changed from new to accepted
comment:7 Changed 13 years ago by jmoore
- Remaining Time changed from 0.25 to 0
- Resolution set to fixed
- Status changed from accepted to closed
"Advanced configuration" modified under:
Referencing ticket #3168 has changed sprint.