Icy Phoenix

hi

I have 722 article in my knowledge base. In few month's I will write more article (more than 200) but when I create a new category now I have this problem:

Quote:

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 5680 bytes) in /home/www/xxxxx/html/merchant-haven/includes/functions_kb.php on line 1082

more than 32mb memory size are not possible for me. With this problem in IcyPhoenix I can't write new article.

I hope that a new patch or a new version fix the memory problem.

p.s. I have read the "How To Reduce CPU Charge On Server " and "How To Reduce SQL Charge On Server " but this don't solve the problem

edit: I must clean my sessions table. I have 30 visitors on a day but the session table has 1200 entrys :roll:

I had that problem too (locally on xampp), when I opened the calendar:

Happens, when I'm in the calendar and click on Calendar on the left small calendar block:



So exceeding the 32 MB and trying to allocate another 25 MB !!!


Also I heard it from a friend, who just changed to IP. 32MB is more than all other forums need. So I presume it's a general problem from IP. Either it doesn't clears the memory or it simply loads too much, althought it might not be needed.

So I think Mighty should go into it and check, what modules are loaded, but not cleared, when loading another page.


regards,
femu

Is there anything in your KB post that requires a lot of processing, e.g. an image?

Generally, IP uses not much more memory than phpbb if all you are doing is posting text in the forum. When you start using other features, such as including an image which needs resizing / effects, then the server needs more memory to process it (this is the same on your own PC, what may appear to be a 256k jpg background image actually requires >100Mb of memory to be displayed - although mostly cached to your hard disk, because thats what the image size is uncompressed - i.e. it requires what its effective size would be if it was a bmp image).

And SQL does not effect the php runtime memory - the effect of deleting old sessions and "reducing SQL charge" simply speeds up the site a little bit, as there are less rows for the SQL server to iterate through. That is, the php server and its allocated memory is completely separate to the SQL server (though they may be on the same physical server, since these two are really daemon services).

I have one image in my kb otherwise only text. I have even delete this image but the problem is beyond :(

I know that this is not the problem, and it would be really good if IP becomes less memory consuming, but meanwhile... have you tried to contact your hosting's technical department and ask they increase the memory for PHP? I had to do it on a site and they increased it a bit so mi problem disappeared.

yes but more than 36mb are not possible and this don't solve the problem at me

Quote:

Fatal error: Allowed memory size of 37748736 bytes exhausted (tried to allocate 118694 bytes) in /home/www/xxxx/html/merchant-haven/includes/functions_kb.php on line 1142

have anybody any other ideas ?

ip is really great but this is only one defect at ip

Have you many categories or many subcategories inside a category or many levels for subcategories? For the line numbers where the errors are I suspect it could be the cause, although I may be wrong.

If you have many categories, subcategories or levels, try to remove some of them or put them to the same level.

yes a have many subcategories but I need they for clearness

edit: my kb >> http://www.merchant-haven.de/kb.php

Yes, I guess it clarify the data organization.

Lets see if what you have is many subcategories at first level, then you cannot do much, as the solution would be put it all at first level, but if the problem is that there is much subcategories levels, with subcategories inside other subcategories, then you can try to organize them in less levels like this:

Quote:

Current organization:

Category 1
..Subcategory1-1
....Subcategory1-1-1
......Articles
....Subcategory1-1-2
......Articles
..Subcategory1-2
....Subcategory1-2-1
......Articles
....Subcategory1-2-2
......Articles
Category 2
...
...

Quote:

New organization:
Category 1
..Subcategory1-1 :: Subcategory1-1-1
....Articles
..Subcategory1-1 :: Subcategory1-1-2
....Articles
..Subcategory1-2 :: Subcategory1-2-1
....Articles
..Subcategory1-2 :: Subcategory1-2-2
....Articles
Category 2
...
...

That is, you can organize it by the name only, reducing this way the number of levels. May be less clear than before, yes, but things like the KB internals cannot be changed on the fly, so you have to find a work around, and it's better a working KB less clear, than a crystal clear KB which doesn't work, isn't? ;)

yes it makes sense. I will test your offer soon. But I have now solve the problem myself. I have restore the auto increment of the database with the database maintenance. Now it works fine

thank you for help ;)