Opened 11 years ago
Closed 10 years ago
#621 closed defect (fixed)
Tile locking performance issue
Reported by: | Dimitar Misev | Owned by: | Kinga Lipskoch |
---|---|---|---|
Priority: | major | Milestone: | 9.0.x |
Component: | lockmgr | Version: | development |
Keywords: | Cc: | Peter Baumann | |
Complexity: | Medium |
Description
Locking seems to have a large overhead, to reproduce
#!/bin/bash rasql -q 'create collection test GreySet' # this will insert an object of 2601 tiles rasql -q 'insert into test values marray i in [0:100,0:100] values 1c tiling aligned [0:1,0:1] tile size 4' time rasql -q 'select sdom(c) from test as c' --out string
Attachments (1)
Change History (14)
comment:1 by , 11 years ago
comment:2 by , 11 years ago
The connection is established once at the creation of the lockmanager instance and closed once at the end of it's work.
comment:4 by , 11 years ago
I submitted another patch that moves the prepared statements into the connect() method. This further improved the performance, so the above query sdom()
query takes 1.6s now.
comment:5 by , 11 years ago
Priority: | blocker → major |
---|
Lowering priority as performance has been substantially improved.
comment:6 by , 11 years ago
A patch simplifying the queries and the table structure was submitted and applied.
I will do further measurements to evaluate the current performance.
by , 11 years ago
Attachment: | lockmgr_measurements.txt added |
---|
comment:7 by , 11 years ago
Above are the measurements I made before and after the performance improvements.
Now, on my university computer, the select needs below 1 second to execute.
comment:8 by , 11 years ago
thanks for providing the results. 2 things I notice:
- select gets slower by a factor of 40 in the optimized lockmgr; we definitely need to work on this.
- insert: the "optimized lockmgr" version is the slowest, slower than unoptimized?
comment:10 by , 11 years ago
Yes, I will submit the patch soon. I wanted to finish my repeated measurements and
add some code documentation and will be able to submit the corresponding patch.
comment:13 by , 10 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
I submitted a patch that drastically reduces the performance overhead, however there is still significant overhead, I assume related to ecpg connections to postgres.
I haven't looked at it, are they established and terminated for every tile or something similar?