Hello everyone, I've got the latest update on what we're doing to help LJ's performance.
Speed up the way our user information is pulled out of the database.
The code release we were originally planning for yesterday has been pushed back to at least Monday.
dnewhall asked for, and received the SQL patches separate from the main release and pushed out
(
Read more... )
Comments 321
Reply
Correct. I was in too much of a rush and didn't explain it correctly. We are only moving ONTD so that is the only journal that will be in read-only mode. Your journal will not be touched, and (except for ONTD), everyone else on your friends list will also not be touched.
bt
Reply
Reply
I don't see your journal as read-only, so I'm assuming by fried you mean it's slow? We're trying to fix the slowness and have implemented a fix for 1 specific problem this afternoon (again, PDT) and will enact another part of the solution tonight.
bt
Reply
Reply
Reply
Wait, is there going to be an issue w/ my LJ? Or just ONTD not showing up on my FList?
Reply
Unless you are the ONTD community, your individual journal will NOT be affected.
It'll be in read-only mode and it will be the only journal like that.
Reply
& Riker <3
Reply
Riker is <3
Reply
That said, I am very glad for the fact that you're actively working on performance influences, and hope LJ's performance improves greatly with the patch and server switch. The SQL patch seems to have made LJ loadable again at least!
Reply
I haven't had any problems with LJ over the past weeks, but today has been absolutely horrible. I could barely access the site all day, it either would not load or kept crashing on me, (it just did it again when I was trying to type up this comment).
I hope all the problems will be resolved soon. :-)
Reply
Reply
wow are you lucky. I wish I could remember what it was like when LJ did work properly :\
Reply
Reply
Leave a comment