mohit | Shared With: Everyone - Sep 24 2008 | mysql, performance, development, replication, technology, databases
There are some helpful tips in here, whether or not you use replication. In my experience, the most important thing with database performance is to minimize the time and row range over which you hold write locks -- and that's what this post is essentially about.
Quoted: Piping data through application is the best solution in many cases and is quite easy - it is trivial to write the function which will take SELECT query and the table to which store its result set and use in your application in all cases when you need this functionality.
mohit | Shared With: Everyone - Feb 21 2008 | books, todo, toread, faves, performance, development, web development
mohit | Shared With: Everyone - Oct 12 2007 | mysql, sql, performance, databases, development, replicationYou have to assume that there will be replication lag. Having said that, chopping up long queries into smaller ones (if using replication) is a good rule of thumb.
Quoted: And the final advice - do not assume very short lag time when planning your application. Having application which can adapt to lag time rather than break is very good idea. Especially it will be handy when you will be reaching replication capacity and will need to buy time to fix things, during which replication lag can be higher than normally.
mohit | Shared With: Everyone - Sep 24 2007 | development, .net, c#, performance
mohit | Shared With: Everyone - Aug 15 2007 | development, mysql, databases, performanceQuoted: Today I would like to share practical example when you may use long primary key with value distribution far from sequential.
...
This table is getting much more reads than writes so transactional overhead of for writes is small price to pay for number of benefits - caching data and index in memory -so cached lookups are very fast, clustering by primary key
mohit | Shared With: Everyone - Jul 24 2007 | development, c#, asp.net, performance, caching, .net
mohit | Shared With: Everyone - Jul 24 2007 | development, asp.net, performance, c#, .net
Some great tips in here.
Quoted: Web App Follies: Keep Sites Running Smoothly By Avoiding These 10 Common ASP.NET Pitfalls -- MSDN Magazine, July 2006
...
LoadControl and Output Caching
Sessions and Output Caching
Forms Authentication Ticket Lifetime
View State: The Silent Perf Killer
SQL Server Session State: Another Perf Killer
Uncached Roles
...
mohit | Shared With: Everyone - Jul 21 2007 | development, mysql, performance, connector, .net
We're using 1.0.7 -- making these changes has helped our performance in our test environment.
Quoted: The 2 I'm mainly interested in are CacheServerConfig and ResetPooledConnections, as in 1.0.7 these made such a difference that (for our application) the connector went from unusable to very efficient. Now, with the 1.0.9 source, it looks like the 3 accepted options for connection reset ("reset pooled connections", "resetpooledconnections", "reset connections") have been replaced with 1: "connection reset". As for CacheServerConfig, it simply doesn't exist any more. The code where it came into play has been changed (if my quick interpretation is correct) to always behave as if it were set to TRUE in 1.0.7. What's the logic of *removing* configurability?
mohit | Shared With: Everyone - Apr 11 2007 | development, mysql, performance, databasesQuoted: Looking at how people are using COUNT(*) and COUNT(col) it looks like most of them think they are synonyms and just using what they happen to like, while there is substantial difference in performance and even query result.
mohit | Shared With: Everyone - Jan 12 2007 | development, mysql, performance, falconQuoted: Now as new MySQL Storage engine - Falcon is public I can write down my thought about its design, which I previously should have kept private as I partially got them while working for MySQL.



