Subject | Re: [Firebird-Architect] Thread priorities |
---|---|
Author | Jim Starkey |
Post date | 2006-11-07T23:02:34Z |
Vlad Horsun wrote:
the code is a great deal easier than changing the architecture, and
changing the architecture is a great deal easier than changing the
mindset of the developers. If you doubt this, look at Firebird. I've
been explaining for well over five years that what I did in 1984 made
sense in 1984 but doesn't make sense in 2001, 2003, 2005, or 2006. Once
developers get holy religion, it is next to impossible to budge them.
This is true at MySQL, Firebird, and the VAX DBMS guys who morphed DEC's
CODASYL database into Rdb/VMS. And operating system guys are even worse.
>>> MS SQL have the similar approach and very happy with it.I haven't tracked MS SQL Server so I can't say for sure, but changing
>>> Google for 'user mode scheduler'
>>>
>>>
>>>
>> MS SQL derived from Sybase SQL Server which was designed around a
>> proprietary Sybase thread system. It isn't the least bit surprising
>> that it performs better with a voluntary scheduler than a general
>> purpose one, but I wouldn't generalize on this at all.
>>
>
> UMS was introduced in MS SQL 2000 which is very far from Sybase
> SQL Server. MS SQL 2000 and MS SQL 4.2 (where MS take Sybase
> SQL Server, iirc) are completely different products
>
the code is a great deal easier than changing the architecture, and
changing the architecture is a great deal easier than changing the
mindset of the developers. If you doubt this, look at Firebird. I've
been explaining for well over five years that what I did in 1984 made
sense in 1984 but doesn't make sense in 2001, 2003, 2005, or 2006. Once
developers get holy religion, it is next to impossible to budge them.
This is true at MySQL, Firebird, and the VAX DBMS guys who morphed DEC's
CODASYL database into Rdb/VMS. And operating system guys are even worse.