Multi threading

[Mike]

Is there anyway to multi thread access or have it use more then 100% of one
core? Example, in a dual core system access with use 50% and on a quad core
it will use 25%. I need access to use 100% whether on a single, dual, or
quad core system.

Or is access just not able to do this?

Thanks

 

[Douglas J. Steele]

AFAIK, Access isn't multi-threaded.

 

[Albert D. Kallal]

Is there anyway to multi thread access or have it use more then 100% of
one core? Example, in a dual core system access with use 50% and on a quad
core it will use 25%. I need access to use 100% whether on a single, dual,
or quad core system.

Or is access just not able to do this?

The problem is that ms-access is not and has not been processing bound for a
good many years.

That means if you double your processing...or even increase your processing
by 10 times, you not see ANY IMPROVEMENT in the running of your application.

Why?

Because ms-access is i/o bound (input/output). that means ms-access spends
all of its time waiting for the network or disk drive. Throwing more
processing at ms-access will not speed up your network or disk drive and
hence you not gain anything by adding more processing.

So, while it would be cool if ms-access was multi-threaded, for the most
part it would not help it run faster.

On the other hand, if you have a duel core pc, and are running two copies of
ms-access then you certainly do gain an increase in code performance, but if
they both hit the disk drive or network...you back to that i/o problem.

ms-access is not limited by processin these days...its the disk drive and
network....

 

[david]

The Access Jet Engine is multi-threaded: it uses 3 threads by default,
controlled by a registry setting. Because it is multi-threaded, it is
difficult to use in a
multi-threaded application: most multi-threaded applications assume that
child processes are single-threaded.

The fact that you see load on only one core indicates that the amount
of processing power consumed by the database engine is trivial, or that
there are no secondary tasks for the other database engine threads to
perform, or that the threads are constrained to run on a single processor.

(david)