查到有几个地方memory leaks,
1、Fix a pair of memory leaks. These were turned up by running valgrind memcheck with various 10k doc insert, update, delete, and query tests
日期为:
2006-Oct-31 18:13:42 (UTC)
2、
The virtual table interface allows for a cursor to field multiple xFilter() calls. For instance, if a join is done with a virtual table, there could be a call for each row which potentially matches. Unfortunately, fulltextFilter() assumes that it has a fresh cursor, and overwrites a prepared statement and a malloc'ed pointer, resulting in unfinalized statements and a memory leak.
日期:
2006-Nov-29 05:17:28 (UTC)
以上来源于sqlite关方网站,现在的最高版本3.3.8
又查到了:
作为数据库引擎SQLite适用于中小规模流量的网站(也就是说, 99.9%的网站). SQLite可以处理多少网站流量在于网站的数据库有多大的压力. 通常来说, 如果一个网站的点击率少于100000次/天的话, SQLite是可以正常运行的. 100000次/天是一个保守的估计, 不是一个准确的上限. 事实证明, 即使是10倍的上述流量的情况下SQLite依然可以正常运行.
面我的系统4(小时)*60(分钟)*60(秒)*5=48000次
搞不清楚,有个朋友说出现过这种问题!
阅读(6593) | 评论(0) | 转发(0) |