> Ideally a given AbstractBuild instance would hold very little in heap, so > that you could scalably loads hundreds of them.
> Perhaps some > kind of lightweight database, or RandomAccessFile / mapped ByteBuffer, > could help this situation, if plugins were updated to keep per-build > information in it? This would be moving toward some kind of abstraction > over Jenkins instance storage, in place of the current getRootDir() > free-for-all. +1 load into the heap as few things as possible, rest refer by weak references so that memory can be freed if needed. In long term add some abstraction layer which would allow to use some database or anything else and let the user choose if database + some cache should be used or everything should be kept directly in the heap
