blocks|key|1218145|text|看看http://code.google.com/p/samstyle-php-framework/source/browse/trunk/inc/cache.inc.php吧。您可以将表(在PHP数组中)保存到缓存中，然后轻松地再次检索它。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1218146|entityMap|0|LINK|mutability|MUTABLE|url|http://code.google.com/p/samstyle-php-framework/source/browse/trunk/inc/cache.inc.php^0|2|2D|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Look at <a href="http://code.google.com/p/samstyle-php-framework/source/browse/trunk/inc/cache.inc.php" rel="nofollow noreferrer">http://code.google.com/p/samstyle-php-framework/source/browse/trunk/inc/cache.inc.php</a>. You can save the table (in a PHP array) into the cache, then retrieve it again later easily.

blocks|key|1218223|text|当速度很重要时，你绝对应该使用memcached。但在大多数情况下，文件缓存或sqlite缓存可以满足您的需求。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1218224|Zend_Cache是一个非常好的缓存库，它通过它的适配器系统支持大量缓存机制，这使得以后更改缓存解决方案变得轻而易举，所以我肯定会选择Zend_Cache。|1218225|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

When speed is important you should definitely go for memcached. But in most cases a filecache or sqlite cache serves your needs.

Zend_Cache is a very good Caching library, the fact that it support numerous caching mechanisms through it's adapter system makes changing caching solutions lateron a breeze, so I would definitely go for Zend_Cache.

blocks|key|1433129|text|也许您可以从检查MySQL查询缓存是否打开开始，如果没有，则启用它。这只需要对MySQL进行配置更改，而不必开始重写或向应用程序添加缓存代码。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1433130|做一些性能测试，如果查询缓存的速度不够快，可以参考其他建议。|1433131|看看这篇关于查询缓存的基本信息的博客文章：http://www.mysqlperformanceblog.com/2006/07/27/mysql-query-cache/|offset|length|1433132|entityMap|0|LINK|mutability|MUTABLE|url|http://www.mysqlperformanceblog.com/2006/07/27/mysql-query-cache/^0|0|0|L|1T|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@$F|S|G|T|1|U]]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

Perhaps you could start by checking if MySQL Query Cache is turned on, and if not, enable it.
This only requires configuration changes to MySQL, and you don't have to start rewriting or adding caching code to your application.

Do some performance tests, and if the query cache doesn't speed things up enough go look into the other suggestions.

Take a look at this blog post for some basic info on query cache:
<a href="http://www.mysqlperformanceblog.com/2006/07/27/mysql-query-cache/" rel="nofollow noreferrer">http://www.mysqlperformanceblog.com/2006/07/27/mysql-query-cache/</a>

blocks|key|1218309|text|打开MySQL中的qcache+(查询缓存)：http://www.databasejournal.com/features/mysql/article.php/3110171/MySQLs-Query-Cache.htm|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1218310|entityMap|0|LINK|mutability|MUTABLE|url|http://www.databasejournal.com/features/mysql/article.php/3110171/MySQLs-Query-Cache.htm^0|N|2G|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Turn on qcache (Query Cache) in MySQL: <a href="http://www.databasejournal.com/features/mysql/article.php/3110171/MySQLs-Query-Cache.htm" rel="nofollow noreferrer">http://www.databasejournal.com/features/mysql/article.php/3110171/MySQLs-Query-Cache.htm</a>

blocks|key|1433213|text|这实际上取决于到底是什么原因导致这些查询速度变慢，以及这些查询是再次是相同的，还是每次都是不同的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1433214|一般来说，我最初会专注于为什么查询很慢并改进它们。数据库内部使用的缓存是高效的，因为不同的查询可以使用相同的缓存项(假设它们使用相同的数据)。|1433215|不要担心MySQL查询缓存，最好使用数据库服务器的ram来增加innodb缓冲池(假设您使用的是innodb)。查询缓存的主要困难在于，当表中的一行被修改时，该表的每个条目都会被抛出-即使该特定查询的结果没有更改。|1433216|如果使用不当，查询缓存可能会严重损害性能-但innodb缓冲池通常只是有益的。|1433217|如果你的数据不是太大，一个便宜和低风险的解决方案是为你的数据库服务器购买大量的内存，并增加innodb缓冲池，使其超过你的数据大小。|1433218|客户端缓存将更具可伸缩性(例如，如果每个web服务器一个)，但效率较低，并向应用程序公开过时的数据(当其数据变得陈旧时，它们可能不会自动过期)。|1433219|就像任何性能的事情一样，测试，测试。使用生产级硬件、类似生产级的数据和工作负载。|1433220|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|S|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|T|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|U|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|V|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|O|$]]

It really depends on exactly what is causing these queries to be slow, and whether the queries are the same ones again, or if they're different every time.

Generally speaking, I'd initially focus on why the queries are slow and improving them. The cache used inside the database is efficient because the same cache entries can be used by different queries (assuming they use the same data). 

Don't bother with the MySQL query cache, your database server's ram is better used increasing the innodb buffer pool (assuming you're using innodb). The main difficulty with the query cache is that every entry for that table gets thrown out when a single row in the table is modified - even if the results of that particular query had not changed.

The query cache can significantly harm performance if used incorrectly - but the innodb buffer pool is generally only beneficial.

If your data aren't too big, a cheap and low-risk solution is to buy your db server lots of ram and increase the innodb buffer pool to exceed the size of your data.

Client-side caches will be more scalable (for example, if one per web server) but less effective, and expose stale data to the application (they will probably not be automatically expired when their data become stale).

As with any performance thing, test, test test. Use production-grade hardware, production-like data and workloads.

blocks|key|1218386|text|如果您只有一个for服务器，并且不需要跨多个服务器分布缓存，那么您可以使用Zend_Cache的APC后端。它比memcached快得多。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1218387|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If you have only one webserver and don't need to distribute the cache across multiple servers then you can use the APC backend for Zend_Cache. It is a lot faster than memcached.

blocks|key|1218427|text|PEAR的Cache_Lite包(+http://pear.php.net/package/Cache_Lite/docs+)是另一个缓存解决方案，您可能也希望对其进行评估。不过，它只使用基于文件的缓存。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1218428|当然，你应该分析那些被证明很慢的查询，看看你是否可以做一些可以让它们更快的事情。|1218429|entityMap|0|LINK|mutability|MUTABLE|url|http://pear.php.net/package/Cache_Lite/docs^0|I|17|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

PEAR's Cache_Lite package ( <a href="http://pear.php.net/package/Cache_Lite/docs" rel="nofollow noreferrer">http://pear.php.net/package/Cache_Lite/docs</a> ) is another caching solution which you might also want to evaluate. It only uses a file-based cache though.

You should of course analyse the queries that are proving to be slow and see whether you can do anything that might make them quicker.

We run a number of web applications written in PHP. Unfortunately there are some select queries within these with some pretty hefty joins which are causing MySQL to become less responsive. 

Because of this we are looking into caching some of the regularly used joins. I have looked into Zend_Cache which looks promising, are there any other alternatives that may perform better?

Also what is the best back end for a cache? I believe Zend_Cache offers file based, Sqlite and Memcached.

Caching in PHP?

性能测试

数据库

服务器

MySQL

我们运行许多用PHP编写的web应用程序。不幸的是，这些查询中的一些select查询带有一些相当大的连接，这导致MySQL的响应变得不那么灵敏。正因为如此，我们正在研究如何缓存一些常用的连接。我已经研究了Zend_Cache，它看起来很有前途，有没有其他可能表现更好的替代方案？另外，缓存的最佳后端是什么？我相信Zend...

问PHP中的缓存？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问PHP中的缓存？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问PHP中的缓存？
EN