Hi, I'm looking into a scalability problem in our current shapefile datastore implementation that prevents fully using the whole CPU(s) once the number of threads hitting the shapefile is > 1.
I only had a cursory look, so I may have misunderstood, but it seems the current locking mechanism tells apart reads and writes api wise (ShpFiles class, acquireRead/acquireWrite methods) but internally uses a basic ReentrantLock instead of a ReadWriteLock. The name of the variable (Lock readWriteLock = new ReentrantLock()) seems to suggest the usage of a ReadWriteLock was attempted... what went wrong? Cheers Andrea ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
