Recently I have revisited the performance issue on my largest project – Diorama.Ru.Â 4000 users with 60.000 page views hitting the server every day. I am proud to have such a “playground” for performance optimization.
We’ve started with the MySQL tuning several months ago, then I have introduced the application level caching using Smarty template engine and finally pushed the last button – Apache gzip compression via mod_deflate.
On the first pages of ABAP Performance Tuning I’ve already learned something new. One of the most powerful methods of the performance tuning is the Kiwi Approach.
Kiwi = Kill It With Iron.
I had an intention to help by informing a webmaster but I didn’t find any single contact (or at least the way to contact the authors) on the whole website. Nothing. Closed like a Black Box.
May be this is a new step in UX evolution, who knows…
Oracle buys Sun Microsystems. It seems this company simply cann’t stop shopping… Peoplesoft, Siebel, InnoDB and now Java and MySQL.
If we call IBM a blue giant should we name Oracle a red one? Or may be a Red Devil?…
Not carrying about Java at all, I’m worried about the MySQL future a bit. I don’t want to see this great project dying. The market sees it different, however.
istockphoto: 1.00 shutterstock: 0.66 fotolia: 0.78
dreamstime: 0.20Â stockxpert: 0.04
Dreamstime and Stockexpert are stagnating on the bottom but Fotolia competes with two other “micro-monsters” on the top. This is quite interesting because it doesn’t exactly reflects the situation with my sales. AlsoÂ according to the regular earnings reports posted by Lee Torrents on Microstock Diaries the picture looks a bit different. You never see the Fotolia in the leaders.Â Very good promotion or am I missing something as a contributor?
Imagine you are a micro stock photograph. Also imagine your are not working exclusively for one agency but contributing to the top 5: iStockphoto, Shutterstock, Dreamstime, Fotolia and let’s say… Stockexpert.
Here is where the problem begins: each agency has its own rules, interfaces, submitting channels (HTTP, FTP etc.). Obviously, as the microstock marked is growing, there is a need for additional services and software both for and contributors and buyers.
I also have a couple nice ideas in this area, soÂ I’ve done a short research on existing microstock API (Application Programming Interface).
Constructing the custom 404 page for Diorama I was looking for best practices. Unfortunately, Wikipedia is not the best place to start in this case. The page itself, however, has several valuable instructions concerning Apache and IIS tuning.
Apart from this: what happens if you get lost by real artist :)