Re: Best database for web backend on Linux?

I am a little confused. Maybe someone could clear this up for me. >I'm not shure, but I think we have a language problem here. What I was suggesting >was all that IO and ancellary CPU time spent managing RLL would go away and thus >improve your performance/capacity. > Given the idea I am updating one record in a particular table. Why would it cost me more to lock the row than the page. I am talking about if I update one record in a table why is it faster for me to place a page lock than a row lock. I have done no benchmarks on this but I have always made the assumption that there is no significant difference in the amount of time it takes to update one record with a row locking scheme that with a page locking scheme. > > >Like I said earlier, no matter how you slice it there is going to be some locking >in you life. The only question I am trying to raise in this discussion is how much >are you willing to pay for it. If I understand your argument correctly, what you >are saying is that you are willing to pay less for development now (presumably >because your design simply isn't acceptable without RLL) and ignore the potiential >cost of capacity/performance based upgrades later. There are definitely times it is ok to sacrifice the speed of batch processes to give a user a faster response time. How fast I update alot of rows in a batch job which has a plenty long enough window to run can be secondary to how long the user has to wait to update one row so he can go on deal with the next row. Will Rice