Many Enteries In One Table

Jul 24, 2013 at 3:11 PM

I was wondering if there is for example 1000000 enteries in one table, should I split it to another tables in order to get better preformance or should I leave it like this?

Jul 24, 2013 at 3:32 PM
Question is not really clear. Are you not satisfied with performance?
Jul 25, 2013 at 9:19 AM
its not that, but I do wanna use the best preformance that dbreeze can offer.
Jul 25, 2013 at 9:58 AM
You don't need to split for the performance. Liana-Trie (search tree of DBreeze) is the same fast for small and big records quantity.

But you can split the entity stream, if it can become partly not interesting for the queries in the future.

For example you collect data every 5 seconds during the complete year 2012 then 2013 ..., but reads are interesting only inside of current month. So, data becomes "old" in a month. It means that every month new table can be created (tbl201306 (june) then tbl201307 (july) then tbl201307 (august) etc) and old table can be deleted. Of course, search algorithm must be adjusted for this.
Aug 6, 2013 at 6:08 AM
you mean tbl201308 (august)... copy paste has side effects... :)
Aug 6, 2013 at 10:25 AM
unruledboy wrote:
you mean tbl201308 (august)... copy paste has side effects... :)
Of course, thank you!
Aug 8, 2013 at 5:42 PM
Edited Aug 8, 2013 at 5:42 PM
Also use transaction.Technical_SetTable_OverwriteIsNotAllowed () for insert performance. But it will raise storage use. If that is no problem,
performance will increase, but after a while it is a good idea is to compact data (recreate tables).