-
eduthie registered the Solubility project.
2005-02-13 22:29:05 UTC in Solubility
-
Thank you for your help.
I discovered the cause of my performance problems.
When doing the testing, before each INSERT or UPDATE query I performed a SELECT query (just to see if the row already existed or not). The combination is what slows it down. Performing the operations seperately is very fast and they do not slow down much when the table size gets into 1 million rows.
2005-01-12 23:14:54 UTC in HyperSQL Database Engine
-
I have a CACHED table with an index created using the following command:
CREATE INDEX index1 ON TableName(column1,column2,column3);
When I perform any query such as SELECT, INSERT, or UPDATE it takes about 1 millisecond if the table is almost empty. If there are 1000 rows in the table it takes about 2 milliseconds. The query time keeps increasing with the number of rows. If there are...
2005-01-12 03:52:39 UTC in HyperSQL Database Engine
