Because they are internal to the groovy script engine? And can't be garbage collected as it is still around and holds handles to those classes. Believe me I would love if there was another way.
Cheers Michael Am 09.12.2011 um 23:53 schrieb Dmytrii Nagirniak: > > > On 10/12/2011, at 9:03, Michael Hunger <michael.hun...@neotechnology.com> > wrote: >> For the first issue we have a work-around in the plugin which recreates the >> script-engine every 500 requests (should probably be configurable) but this >> is less than optimal. > > That is just rediculous workaround as to me! You drop everything that the > engine carefully tried to compile and optimize! This defeats the point of the > optimization. > Why not use a priority queue/list/cache and drop the entries that are least > used only? > > _______________________________________________ > NOTICE: THIS MAILING LIST IS BEING SWITCHED TO GOOGLE GROUPS, please register > and consider posting at https://groups.google.com/forum/#!forum/neo4j > > Neo4j mailing list > User@lists.neo4j.org > https://lists.neo4j.org/mailman/listinfo/user _______________________________________________ NOTICE: THIS MAILING LIST IS BEING SWITCHED TO GOOGLE GROUPS, please register and consider posting at https://groups.google.com/forum/#!forum/neo4j Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
