Is Access 2002/2003 a multi-threaded application. Will is support
Hyper-threading.
Thanks,
It is possible that some of ms-access can have more then one thread, but as
a general rule, I don't think this is the case. On the other hand, I can't
possibly imagine ANY performance gains and benefits from it being threaded.
Any bottle neck with ms-access is going to be that of the database engine,
and the speed of the disk drive for that engine. So, if you are uses
ms-access to get data from oracle, or to get data from sql-server, ms-access
will not be the problem.
On the code side, we have little, or no limitation in terms of processing.
It is all about bandwidth to the data...and threading will not help this.
You can use VB, c++, or ms-access to grab JET data, or to grab data from sql
sever...and they all will performance the same.
So, your bottle neck will not originate with ms-access, but the disk drives,
and the data engine used....
The little disk based JET data engine is very fast as is. That engine can
grab, sort, and total 100,000 inventory records against invoices, and also
a table of inventory added records in less then one second anyway. And, the
waiting time is still 90% disk time and I/o time.
Of course, a file 100,000 invoice details records is VERY small, but JET can
grab that kind of thing and match it up against precuts sold to get a total
in less then one second.....
And, hyperthreading in most benchmarks only gives about 20% anyway. That
means a 13 second operation would take only 10.4 seconds. However, of that
13 seconds....99% of it is waiting for the data, and is not processing
bound. So, that 20% improvement would only apply to the 1 second (or less)
of processing here...and you can't going to notice that at all. (you likely
are going to save .2 of a second).
Hyperthreading and a threaded application will not help performance in any
noticeable way here. Hardware to day is so fast, that any performance issue
that arises in ms-access is usually the result of poor setup, or poor
design, or limited bandwidth. Processing is not the problem with ms-access,
and rarely is.....
