Hi Sergei, In your patch, you added support for memory indexes. But memory indexes are already supported (you just need to create memory tables, then all indexes are automatically memory indexes).
Could you write and run a simple performance test against the regular implementation and against your patch, and show me how your patch improves performance? The H2 Console supports simple performance tests using this (undocumented) syntax: DROP TABLE TEST; CREATE MEMORY TABLE TEST(ID IDENTITY, NAME VARCHAR); @LOOP 10000 INSERT INTO TEST VALUES(?, 'Hello'); @LOOP 100000 SELECT * FROM TEST WHERE ID=MOD(?, 10000); @LOOP 100000 SELECT * FROM TEST WHERE ID=MOD(?/*RND*/, 10000); DROP TABLE TEST; CREATE TABLE TEST(ID IDENTITY, NAME VARCHAR); @LOOP 10000 INSERT INTO TEST VALUES(?, 'Hello'); @LOOP 100000 SELECT * FROM TEST WHERE ID=MOD(?, 10000); @LOOP 100000 SELECT * FROM TEST WHERE ID=MOD(?/*RND*/, 10000); Just change the CREATE statement(s), loop count, and JDBC URL. You should run each test multiple times and check the last result. Regards, Thomas On Wed, Mar 11, 2009 at 10:14 PM, Thomas Mueller <[email protected]> wrote: > Hi, > >> I've sent the patch on your mail. Did you look? > > Thanks for the patch! I didn't have time to test it yet, I will do > that as soon as possible. > > Regards, > Thomas > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/h2-database?hl=en -~----------~----~----~----~------~----~------~--~---
