Resources are likely to be considerably faster and more compact than class files. The issue is that the class files actually compile into code that inserts values one by one. Better to just read the whole table in a single go directly into an array.
On Thu, Sep 15, 2011 at 9:21 AM, <luc.maison...@free.fr> wrote: > > If going in that direction (not discussing whether this good or bad), > > I would say that we should surely not use litteral arrays but look at > > those > > tables as "resources" and load them with the appropriate > > functionality. > > This would then most clearly set them apart from the "real" code. > > If you think another way to load the tables is better, then go for it. > I really don't care about how it is done. I just want it to be done fast. > We can use serialized data in the embedded resources if it is fine with > you. >
