This is a pretty simple approach I often use called to optimize web application performance if problem happens with few pages. If we have “everything is slow” problem looking at slow query logs may be better start.
So what could you do ?
Look at the information shown on the page which comes from database. […]
When I loaded GigaBytes of XMLs into mysql database with PHP script, I was thinking about PHP alternatives. Why do I need that ?
1. PHP is slow – I’m speaking about area of data processing and implementation of algorithms
2. No good cli debugger – I’m just tired of debugging with ‘echo’ and ‘var_dump’
3. Unpredictable […]
Have you ever seen index which refused to be used even if there is every reason for it to work (from the glance view):
mysql> explain select * from article where article_id=10;
| id | select_type | table | type | possible_keys | key | key_len | ref | rows | […]
InnoDB uses its own mutexes and read-write locks instead of POSIX-mutexes pthread_mutex*, the main reason for that is performance, but InnoDB’s implementation isn’t ideal and on modern SMP boxes can cause serious performance problems.
Let’s look on InnoDB mutex (schematic for simplification):