Doug Nebeker wrote:
Yes I did the same experiment with a lock that made thread A wait
until B was finished. So actually only one thread can be active at
the time.
I don't see how the outcome of this experiment can be of any
interest, as there is no time reduction any longer. But your guess
is
right that, it works.
How would multiple threads be faster than a single one when you are
accessing a single resource?
Assumably the thread that is accessing the database either spends some
time gathering data to write
or processing data it read. The single resource isn't in use during
that time.
I just notice that threading is often misunderstood. It is a way of
sharing resources, not of making single resources, like a CPU or a
database handler using a single disk drive operate faster.
This email was sent to you by Reuters, the global news and information company.
To find out more about Reuters visit www.about.reuters.com
Any views expressed in this message are those of the individual sender,
except where the sender specifically states them to be the views of Reuters Limited.
Reuters Limited is part of the Reuters Group of companies, of which Reuters
Group PLC is the ultimate parent company.
Reuters Group PLC - Registered office address: The Reuters Building, South
Colonnade, Canary Wharf, London E14 5EP, United Kingdom
Registered No: 3296375
Registered in England and Wales
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
