the kabulpress.org is too slow ( if you speak about kabulpress.org)
In my case ( dedicated server 50 000 uniq visitors, 20 000 articles)
SPIP+Magento+10 mailists
I did:
1. Make mysql option
slow-query on
http://dev.mysql.com/doc/refman/5.1/en/slow-query-log.html
I had found that bot was submiting internal search and it was the
slowest queries that made a dead-lock on database.
I'd remove the internal search toward Google
2. Mysql speed tuning - encreasing the buffers, number of connections
( many docs in the internet descibing it, if any matters - write to me
and I will send my config)
3. I've created the RAM filesystem and have put there directories:
/local/
/tmp/cache/
4. I've limited the total size of cache to 300Mb, and made some
increasing of article, rubrique cache
I think the best you could do - to log the slowest query and analyze them
Best regards,
Serge
2010/5/11 Gilles VINCENT <gilles.vincent@gmail.com>:
Hi Kamran,
you can also try the plug in Expresso and cache cool :
The first one creates a static cache in front of the dynamic cache of SPIP
The last one changes the process of computation of the cached files : they
are calculated when the server isn't loaded, and not when the user requests
a "Please calculate me" page.
On Tue, May 11, 2010 at 10:53 AM, klaus++ <klaus@spip.de> wrote:
On the webmaster-level you may give the per-page cache a longer timeout:
#CACHE{seconds}
e.g.
#CACHE{3600} one hour
#CACHE{3600*24} one day
#CACHE{3600*24*7} (one week)
Put this at the very beginning of your pagees.
This may not be enough : when an article is modified, all the cached files
where it may appear are flagged as "Please calculate me, I may not contain
the latest datas". Then, at the next round, the database may have to manage
too much requests..
.Gilles
klaus++
kamran Mir Hazar wrote:
Hello,
I give the following error everyday mostly when I do update my site or
there are new syndicated articles that are going to be publishing
automatically. I’m sure there are also multiple visitors on the site at the
same time. It was over two million hits and over 100 GB Bandwidth usage
since May 01, 2010:
Warning: a technical problem (SQL server) prevents access to this part of
the site. Thank you for your understanding.
There is no any problem with config file and the database name and login
info. Just in November 2009, I gave the same error and it was fixed by
moving the database to another server. Is there any solution for this
error?
There are more than 10300 articles published on my site. Do you think
there is any limitation for articles published in SPIP system?
Thank you
Kamran
------------------------------------------------------------------------
_______________________________________________
spip-en@rezo.net - http://listes.rezo.net/mailman/listinfo/spip-en
_______________________________________________
spip-en@rezo.net - http://listes.rezo.net/mailman/listinfo/spip-en
_______________________________________________
spip-en@rezo.net - http://listes.rezo.net/mailman/listinfo/spip-en