On 07/26/2011 10:19 AM, Karsten Hilbert wrote: [KSB4] Correct, for local processes, GT.M is not a database server. Database management occurs through cooperation between the processes accessing it. What this means is that GT.M database throughput often goes up as the number of processes accessing it increase - depending on the application workload, this is often two to four processes per CPU/core. There is actually a database server (GT.CM) that serves databases on remote machines via a protocol layered on top of TCP. But the GT.CM server processes themselves run on the system like normal user processes. Another "surprise" for people in the database world is that GT.M uses optimistic concurrency control to implement ACID (Atomic, Consistent, Isolated, Durable) transactions. Regards -- Bhaskar -- GT.M - Rock solid. Lightning fast. Secure. No compromises.
_____________
The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. _____________ |