[fdo-internals] SDF 3.0 FDO Provider Serious Memory Leak
carl.jokl at keynetix.com
Tue Jul 15 05:57:32 EDT 2008
So looking at thread safety in general. I have not used multithreaded FDO
manipulation. Judging by what I have seen so far I would think it risky.
I also don't know if any multi-threading is used by the native C++ code. I
did wonder if that could improve the performance of the PostGIS FDO driver
perhaps. Potentially one thread busy pulling raw data from the database (IO
Bound thread) with the other busy restructuring it into the FDO required
format (Processor bound thread). The next batch or raw data being loaded
from the database while the previous batch is still being restructured into
FDO. As I understand it though multi-threading is not built into C++ and
requires native platform code to create new threads.
View this message in context: http://www.nabble.com/SDF-3.0-FDO-Provider-Serious-Memory-Leak-tp18447913p18461604.html
Sent from the FDO Internals mailing list archive at Nabble.com.
More information about the fdo-internals