URL to your eFiction: http://www.jonasbrothersfanfictionarchive.com
Version of eFiction: 3.5 (running 3.4.3 stories.php)
Have you bridged eFiction, if so with what?: SMF
Version of PHP: 4.4?
Version of MySQL: 5
Have you searched for your problem: yes
If so, what terms did you try: spike cpu
State the nature of your problem:
We're having MASSIVE cpu spikes. Incredibly massive. 250mb to 4000mb kind of massive.
Unfortunately, we're on Dreamhost VPS and we don't quite have the kind of logging access I'd like, so I'm not sure where this apparently massive error is coming from. I highly suspect it's the e-mails going out when a really popular story updates. We have almost 10,000 members so some of these stories have a ton of favorites.
It could also be an issue with SMF, but the SMF error log isn't giving me any unsual reports just people forgetting passwords and such.
And finally, there's the problem with stories.php. Unfortunately, we have co-authors on and the only solution to the problem for 3.5 seems to work for people with it off. I don't know if that's breaking things.
I've tried replacing all the files. I've tried optimizing the database. I've tried blocking spiders. I've tried looking at stories.php but I don't understand enough php. I've tried resetting everyone's e-mail settings to not send when a favorite is updated. I thought about decoupling SMF and eFiction, but wasn't sure if I could put humpty dumpty back together again.
ETA: I just turned debug on, and I don't see to be pulling any errors.
Do you have a test account for us? testuser/banana
Skins made by Kali are no longer supported!
I'm not sure what I can do to help knowledge-wise, but I run a comparably-sized archive. (More members, but fewer stories.) For my own purposes, I've actually set up a copy of the site. Basically, it's the same database but with a new 3.5 (modified stories.php) install of the files. (Also, no stories folder, so no story text.) If that might be at all helpful to you as a testing ground or for comparison, let me know.
Will Dreamhost not tell you? :s
archive:
site:
Available for skin/mod commission! 🙂
Dreamhost just said, Oh hey, massive errors, buy more space. They couldn't even answer where the error was coming from, just that it said something about Error 1. Thanks Dreamhost!
Skins made by Kali are no longer supported!
Useful. 😐
Blah, I've Googled, but I don't seem to be coming up with anything relevant. Sorry.
archive:
site:
Available for skin/mod commission! 🙂
Thank you for the effort. We've been dealing with this for almost 2 months now with, so I didn't think there would be an easy fix. At this point I might consider hiring an expert to go through the code for us.
Skins made by Kali are no longer supported!
I remember reading something about eFiction and indexing. Perhaps you could look into that?
archive:
site:
Available for skin/mod commission! 🙂
I remember reading something about eFiction and indexing. Perhaps you could look into that?
You mean like caching?
Well, disabling the e-mail alerts cut down on the 500 errors when popular authors updated, but we're still experiencing them. I also finally got the 3.5 stories.php working.
I'm still debating de-bridging SMF, but I don't think I can really reverse that unless I somehow disable the registration during the day I do my testing. Otherwise I don't even want to think of how out of sync the databases will be.
Skins made by Kali are no longer supported!
