Brad Fitzpatrick's LiveJournal[Most Recent Entries] [Calendar View] [Friends]
Below are the most recent 20 journal entries recorded in
Brad Fitzpatrick's LiveJournal:
- did my laundry, but haven't folded them.
- I now have shorts on.
- I got two new DVDs in the mail today, making 5 total that I've yet to enter into my DVD database.
- LiveJournal is being cooperative
| Tuesday, June 27th, 2000 | |
| 6:21 pm | No more bugs? Okay, I think I got the last of the LiveJournal "bugs" worked out .... the latest bug that was causing so much trouble was that I still had the old server running, so some people's DNS wasn't properly updated and they were using the old server (w/ the old code). Anyway, I setup mod_proxy on that machine to just ProxyPass everything to the new server for now, until I nuke that one and rebuild it, at which time I'll do some intelligent load balancing between the two. |
| 6:04 pm | Silly X Weird ... my ALT key stopped working. Had to stop and restart X. |
| 4:18 pm | Heh I just got an email message from one of my old co-workers .... we're both subscribed to the MySQL mailing list and he just saw a reply I posted. :-) |
| 3:58 pm | Afternoon Excitement Here's my big happenings of the afternoon: |
| 1:48 pm | No thanks. This person just wrote to me at the FreeVote help-translate address: dear who may coreonYeah, sure, you can almost read/write English, so I'll let you translate the site! *rolls eyes* |
| 1:03 pm | laundry time Time to do some laundry ... I have literally no clothes left: I've been sitting around in boxers all day. I think that's the best part about working from home -- you don't even have to get dressed. |
| 11:23 am | Awake. Just got up and guess what? LiveJournal's alive!! Frickin' amazing. Maybe I'll go back to bed or something. |
| 1:55 am | *sigh* no critical problems tonight so i should be able to sleep, but there are still some things kinda bugging me that i want to get done before I go up to visit Blythe from the 29th-4th ... going to bed now. |
| Monday, June 26th, 2000 | |
| 10:58 pm | Green Mile ... weird Okay, Green Mile just got weird ... the big dude is grabbing people's nuts and breathing insects out of his mouth or something. |
| 9:49 pm | or not i brushed my teeth and washed my face and that woke me up a bit ..... watching Green Mile now. |
| 9:40 pm | dead Current Mood: Dead Fawkin' Tired. Think I'll be going to bed now .... didn't really sleep last night. The remaining LiveJournal optimizations will have to wait. |
| 7:32 pm | .. more livejournal speed-ups One of my favorite ways to optimize database applications is to enable db logging and then just tail the log file and watch how many unecessary queries are happening, then go try and clean them up. for instance: I noticed that if you were logged in and went to look at your own journal, it would pull your user record twice from the database: once to render the page, which is always necessary, but then also once to verify your login password with your login username ... I rearranged a bunch of code and now it pulls the full page owner's user record first (before it was doing remote user authentication first) so then when it comes time to authenticate the user, I can check and see if the remote user is the page owner, and thus prevent an extra query. |
| 6:16 pm | Hmmm I wish perl had static variables. I like that about C. |
| 4:17 pm | |
| 3:42 pm | Hell fuckin' yeah! So you know how I was complaining about MySQL having that bug last night? I sent in my intelligent bug report (it's amazing how many clueless users there are on that list) with my table definition and a test case which crashed it and last night I was contacted by them asking me to upload to their private FTP area my table files .... I did that, and now they just sent me a patch which fixes it ..... they're frickin' amazing. Time to patch mysqld and get workin' on LJ again.... |
| 1:55 pm | Grrr Yes, LiveJournal was down all morning, but you should've seen how fast it was before it crashed! *sigh* The problem is MySQL crashing whenever it does something complicated..... I've sent in a bug report and they're apparently working on it, analyzing LiveJournal's database files. In the meantime, I'll be improving my "watching-LiveJournal-while-I-sleep" script to be aware of more potential problems (like the database server dying) ... currently it only checked for the web server being retarded. |
| 6:11 am | no sleep. can't sleep. not even tired. ;-/ |
| 5:04 am | db bugs & bedtime I was getting a lot done, but then I found a bug in the new version of MySQL. I was thinking about just being pissed off and finding a way around it, but instead I took the time to join the MySQL mailing lists and send in an intelligent and detailed bug report... hopefully it'll get fixed. In the meantime, I think I have found a way around it, but I'm tired and don't care now. I'm going to bed. |
| 3:37 am | LOL! Oh my. Check this out ... frickin' hilarious. :-) |
| 3:31 am | Sleep? Naah. I was really planning on going to bed early tonight, but the past few hours I keep finding really cool things that I could change in LJ to make it faster. I've sped up the "recent entries" display page in the same way I sped up the friends page the other day, but now I realize there are other places in the code where I do similar slow queries (like when you're in the windows client and select to modify the most recent entry) that could be improved by abstracting my "get the last n entry IDs of { lastn | friend } type" code. so that's the current project. it'll involved rearranging a lot of the code, but it should be a lot quicker in the end. |