Re: Performance problems with the TikiWiki
That's right, Gary. I understand.
But the point I am making is that when there is a TW running, and there is an exploit as large as the moon, and that is a serious problem.
You don't need to be a specialist to see what is going on. An example.
1. Run phpMyAdmin and choose the tab processes.
2. Log into TikiWiki and you see several processes to the database (including the SQL-statements).
3. When you refresh, those processes are gone.
4. Then go to the file gallery of the TW and download a file
5. You see a process to the database and it stays like that
6. When the file is finished downloading, the process disappeared
7. When the user closes or cancels the download, the process still hangs there for hours! 😧😧😧
The MySQL database engine is nice, but limited, just like any software. It is able to support a certain number of database connections.
So, when I take a good download manager, and I download 30 files at the same time or more, and others do the same, the MySQL gives an error "Too many connections" and stops working ... for the server and all relevant websites will crash!
When I try to restart the server, it refuses, because there are still connections towards the database. The only way (quick way) to continue is rebooting the server and we can continue.
What I want to say is that this behavior makes it impossible to use the file- and image galleries in public (as are the attachments), which is so fantastic in the version 3. When I offer files for download, I will take the risk that the server will stop working. And it does not help to add memory, processors and the whole thing.
I personally love the TW, but it is not possible to use the software in production environment. And it is absolutely not possible to use it in public!
And it's a pity, because I managed to combine in a way forums and TW without any impact and no customizations.
-
What I am talking about is not a feature or an issue of performance, but I am talking about the fact that the TW keeps a database connection open to the database while a file is being downloaded. The programmer knows about databases, I assume, and he also knows that the number of connections are limited, and he also knows how more connections to the database, how slower the engine becomes!
It does not show at the CPU load or any other performance number of the server, the end user detects it, it becomes too slow and takes too long to go from one page to another.
When I take my TW, open the first page, then go to the File Gallery, I must wait 33 seconds before it is there.
When there are about 40 database connections open, I must wait for almost 3 minutes before the page appear. But my CPU load is only 0.3!
I can guarantee you that if you solve that issue with the database connections, the TW will fly for the user (maybe a bit more CPU, but you can do something about that. The database connections stops everything and there is nothing for me left to go to another system! Sorry about that.
Now I have galleries, which are maybe not as useful as the TW one, but it is fast and does not need any database connections. Now I support up to 200 downloads at the same time without impact on anything. The TW supported about 30 downloads before the thing became so slow for everyone, that you hardly could load any page. And I'm talking about a 4Gb dual processor machine.
-
About the bug reports?
I reported most of the bugs except the last one. The only reaction I saw that the developer acknowledged the report and his answer was that he could not repeat it.
A week later the version 3.1 came out and there was no change in that bug. I can easily reproduce it with a test page, but your programmer seemed not to be able to do so. Even when I explained how to do it, I never heard from him again.
Some other issues I also posted, but no reaction at all. After a while I give up.