I am not sure if it is because the person writing doesn't speak English as the native language, but this can't be right <http://orientdb.com/docs/1.7.8/orientdb.wiki/Performance-Tuning.html#keep-the-database-small>, as a performance tuning tip.
*Keep the database small* > The smaller the database you have, the bigger are the number of records > you can cache in memory. Furthermore small database means faster seek in > filesystem and minor loading time from disk/network. In order to keep your > database small follow the following suggestions: > *Keep field names short* > OrientDB is schema-less that means field names are stored with the values > too. So if you call a field "out" instead of "outVertices" you saves 8 > characters, namely 8 bytes per record. Applying this to millions of records > allows you to save several Megabytes. I understand about disk space savings with small field names, however, that is purely a userland decision and shouldn't have a large impact on overall database performance. So, is this really meant as a tip for performance tuning? Because, I thought OrientDB is also built for scale with large data sets. Scott -- --- 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 orient-database+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
