orientdb 2.0.5 I have a database in which we create non-unque index on 2 properties on a class called indexstat.
The two properties are made up of a string identifier plus a timestamp. Data is created in batches of few hundred records every 5 minutes. After a few hours old records are deleted. This is file listing are the files related to that table. Question: Why is the .irs file which according to documentation (is related to non-unique indexes)...so monstrously huge after a few hours. 298056704 bytes larger than actual data (.irs size - .sbt size - .cpm size). I would think the index would be smaller than the actual data. Second question: What is best practice here. Should I be using unique indexes instead of non-unique? Should I find a way to make the data in the index smaller (e.g. use longs instead of strings as identifiers)? -rw-rw-rw- 1 root root 727778304 May 11 08:51 indexstat.cpm -rw-r--r-- 1 root root 1799095296 May 11 08:51 indexstatidx.irs -rw-rw-rw- 1 root root 263168 May 11 08:51 indexstatidx.sbt -rw-rw-rw- 1 root root 773260288 May 11 08:51 indexstat.pcl The -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
