I have been looking at Datomic/Datalog which abstracts away the container entirely and focuses simply on entity, attribute, value + time deltas. In theory, the underlying container(s) could adjust to optimize for typical, and possibly changing, usage patterns. Worth a look and some consideration :-)
Alan M. On Fri, Jan 4, 2013 at 7:48 AM, Marcus G. Daniels <[email protected]>wrote: > On 1/4/13 4:04 AM, Ondrej Bilka wrote: > >> Profiling will reveal that you spend 5% time in insert and 3% time in >> remove. You spend two weeks optimizing your tree and memory allocator >> for it. >> > The call tree, accumulating these costs in different parent contexts, when > correlated to the fact that (presumably) the containers being acted upon > are different containers, can suggest a change to a specialized container > type depending on the access pattern... > > > Marcus > ______________________________**_________________ > fonc mailing list > [email protected] > http://vpri.org/mailman/**listinfo/fonc<http://vpri.org/mailman/listinfo/fonc> > -- *"Whatever you can do, or dream you can do, begin it. Boldness has genius, power, and magic in it. Begin it now."* - *Goethe*
_______________________________________________ fonc mailing list [email protected] http://vpri.org/mailman/listinfo/fonc
