New server and ST
jfranco 0
From: -
From: -
Notice
This topic is archived. New comments cannot be posted and votes cannot be cast.Responses to this topic
1 Re: New server and ST
Jason Amison 0
From: -
From: -
New server and ST
Phillip,
Sorry to comment in this thread Julio, but I believe xCache outperforms APC. Not only that, APC has had numerous issues in it's last couple of releases, well so I've heard. Maybe you can clear me up on this issue? There again, I've heard that Xcache can be buggy for some.
Regards Jason
Phillip,
Sorry to comment in this thread Julio, but I believe xCache outperforms APC. Not only that, APC has had numerous issues in it's last couple of releases, well so I've heard. Maybe you can clear me up on this issue? There again, I've heard that Xcache can be buggy for some.
Regards Jason
1 Re: New server and ST
Philipp
From: Austria
Administrator
1342From: Austria
New server and ST
I enabled PHP error messages output and MySQL strict mode on my development server to debug PHP code.
However, it would be pointless to enable both on a production server after many older PHP scripts will not work properly or with many warnings in this configuration. Contentteller is one of a few scripts that can run with the strictest PHP/MySQL settings.
Now I know it has to be something I have customized over the years... any ideas where should I start, or a good way to troubleshoot PHP code? You have way more experience at that than I do for sure.
I enabled PHP error messages output and MySQL strict mode on my development server to debug PHP code.
However, it would be pointless to enable both on a production server after many older PHP scripts will not work properly or with many warnings in this configuration. Contentteller is one of a few scripts that can run with the strictest PHP/MySQL settings.
1 Re: New server and ST
jfranco
OP
0
From: -
From: -
New server and ST
Thanks for the input Philipp. I yet have to heavily troubleshoot the new server and look where the magic quotes error is being generated. But asking you was a good first step
.
Now I know it has to be something I have customized over the years... any ideas where should I start, or a good way to troubleshoot PHP code? You have way more experience at that than I do for sure.
PS: APC is now installed on our new server.
Thanks for the input Philipp. I yet have to heavily troubleshoot the new server and look where the magic quotes error is being generated. But asking you was a good first step
.Now I know it has to be something I have customized over the years... any ideas where should I start, or a good way to troubleshoot PHP code? You have way more experience at that than I do for sure.
PS: APC is now installed on our new server.
1 Re: New server and ST
Philipp
From: Austria
Administrator
1342From: Austria
New server and ST
Storyteller should work with both magic quotes on and off. Where is exactly the problem?
The InnoDB storage engine has overall a higher reliability in a high traffic environment, at least in the past. MyISAM in MySQL 4.1/5.x is nowadays also quite reliable and have even a few features that InnoDB doesn’t have.
Contentteller will automatically use the default MySQL storage engine (usual MyISAM) and no longer defaults to InnoDB.
I highly suggest APC cache http://pecl.php.net/package/APC after it will be included in PHP 6
I found that ST didn't want to work with php's magic quotes off, is this a requirement on this version or could it be some custom coding we put in place during the years?
Storyteller should work with both magic quotes on and off. Where is exactly the problem?
When testing Storyteller I got prompted at some point for upgrading the MyISAM databases to InnoDB, should I upgrade? Could you briefly tell me in terms of ST what's different and what's your insight given that we will eventually move to CT?
The InnoDB storage engine has overall a higher reliability in a high traffic environment, at least in the past. MyISAM in MySQL 4.1/5.x is nowadays also quite reliable and have even a few features that InnoDB doesn’t have.
Contentteller will automatically use the default MySQL storage engine (usual MyISAM) and no longer defaults to InnoDB.
In our current server we used Turck cache for a while, then moved on to eAccelerator. We have yet to install anything similar to this on the new server, what are your experiences with newer similar technologies and do you recommend any given the eventual upgrade to CT as well?
I highly suggest APC cache http://pecl.php.net/package/APC after it will be included in PHP 6
Hi Philipp,
We are currently moving to a new faster server and I wanted to hear what your opinion is on a number of things. We have kept RHEL as our OS although upgraded to v5.1 which also puts us up to date on PHP and mySQL.
So far I have found no big problems moving StoryTeller over, but here are a couple of questions that relate to the upgrade...
I found that ST didn't want to work with php's magic quotes off, is this a requirement on this version or could it be some custom coding we put in place during the years?
When testing Storyteller I got prompted at some point for upgrading the MyISAM databases to InnoDB, should I upgrade? Could you briefly tell me in terms of ST what's different and what's your insight given that we will eventually move to CT?
In our current server we used Turck cache for a while, then moved on to eAccelerator. We have yet to install anything similar to this on the new server, what are your experiences with newer similar technologies and do you recommend any given the eventual upgrade to CT as well?
Thank you!
Julio