I was trying to reduce the memory footprint for the page iterations. (sf.net fails on AllPages, if count > 300).
I'm still working on this...
It's not a memory leak, just trying to reduce the requested pagedata columns.
* _cached_html only for pages which must be rendered,
* versiondata.content only for requests which require the content.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Tryed to use the night phpwiki in produktion environment und limited AllPages to '100'. But no way, there are several httpd processes using so much memory the the nobody can really use it. have to wait until the problem is fixed.
Thank you and regards
Stefan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Tryed to use the last nightly build date 11 jul 04 and it also uses more than one gig of memory when trying to start AllPages without limit (a little more than 5400 pages in the wiki).
Should it be fixed or are you allready working on it?
Saw some changes in the phpwiki changelog that made me hope it where fixed.
sorry if i'am to impatient
Regards Stefan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
the nightly build needs so much memory when starting AllPages.
1 Gig of swap memory and 500 meg of memory whats going on here? And the page was never shown ....
the rest works fine
regards stefan
i tested the same with 1.3.9 it only uses 51 meg of memory .... wow, big memory leak
I was trying to reduce the memory footprint for the page iterations. (sf.net fails on AllPages, if count > 300).
I'm still working on this...
It's not a memory leak, just trying to reduce the requested pagedata columns.
* _cached_html only for pages which must be rendered,
* versiondata.content only for requests which require the content.
Tryed to use the night phpwiki in produktion environment und limited AllPages to '100'. But no way, there are several httpd processes using so much memory the the nobody can really use it. have to wait until the problem is fixed.
Thank you and regards
Stefan
Tryed to use the last nightly build date 11 jul 04 and it also uses more than one gig of memory when trying to start AllPages without limit (a little more than 5400 pages in the wiki).
Should it be fixed or are you allready working on it?
Saw some changes in the phpwiki changelog that made me hope it where fixed.
sorry if i'am to impatient
Regards Stefan
No, apparently it's not fixed yet.
Still working on it. (basically testing against older releases).
To my understanding it should have been improved, but it got worse...
ok thats fine ...
i saw that the load time of the startpage of my wiki is sometimes much slower then that from 1.3.9 so i changed back to 1.3.9.
new wiki:
http://www.mineralienatlas.de/phpwikinew/index.php/StartSeite
old wiki:
http://www.mineralienatlas.de/lexikon/index.php/StartSeite
Regards Stefan
ADODB or PearDB?
ADODB is my favorite pet now and should be much faster.
I don't touch much at PearDB.
i use adodb
DATABASE_TYPE = ADODB
DATABASE_DSN = "mysql://user:pwd@localhost/lexikon"
DATABASE_PREFIX = "wiki_"
DATABASE_SESSION_TABLE = session
the old one is mysql
Regards Stefan