Opened 9 years ago
Closed 9 years ago
#1032 closed defect (fixed)
parallel query not working
Reported by: | George Merticariu | Owned by: | George Merticariu |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | undecided | Version: | development |
Keywords: | Cc: | Peter Baumann | |
Complexity: | Medium |
Description
if two retrieval (select) queries are executed, then the second one is waiting for the first one to finish.
e.g.
console 1: ./rasql -q 'select avg_cells(test - test/2 -test/3) from test' —out string
console 2: ./rasql -q 'select avg_cells(test - test/2 -test/3) from test' —out string
Result: Console 1 is executing, Console 2 is waiting → Console 1 finishes, Console 2 is executing → Console 2 finishes
Change History (7)
comment:1 by , 9 years ago
comment:2 by , 9 years ago
We have a bit of a problem with SQLite that is just becoming apparent — SQLite is great for a multithreaded application, but not very optimal for our multiprocess environment.
I tend to think more and more that traditional PostgreSQL + filesystem for the tiles is the optimal backend for rasdaman.
comment:5 by , 9 years ago
Yes most likely, but I didn't expect it to affect purely select queries. It needs to be revised.
comment:6 by , 9 years ago
I submitted a patch, the issue was in starting IMMEDIATE transaction rather than regular one, which prevents other IMMEDIATE transactions to be started until it finishes.
comment:7 by , 9 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Hmm this shouldn't happen with select queries..