S
Siegfried Heintze
I have a screen scraper populating my Access database. Assuming that network
latency is not the bottle neck, can I expect multiple threads or processes
populating the same access database simultaneously to populate it faster?
I thought MSAccess was single threaded and locked the entire database file
whenever there was an INSERT or UPDATE in progress and therefor having
multiple processes or threads would not improve the thru put.
Presently I have two different MSAccess database files being populated by
two different screen scrapers so the two different processes are not
competing for the same database. I am surprised to see that each process is
running as fast as it did when running solo. How could this be?
Thanks,
Siegfried
latency is not the bottle neck, can I expect multiple threads or processes
populating the same access database simultaneously to populate it faster?
I thought MSAccess was single threaded and locked the entire database file
whenever there was an INSERT or UPDATE in progress and therefor having
multiple processes or threads would not improve the thru put.
Presently I have two different MSAccess database files being populated by
two different screen scrapers so the two different processes are not
competing for the same database. I am surprised to see that each process is
running as fast as it did when running solo. How could this be?
Thanks,
Siegfried