Monthly Archives: October 2008

Cached

As most people probably can discern by reading the backlog of content entries here, I’m a fan of Memcache. It makes database driven applications crazy fast when used properly, and can be damn simple to integrate if your code is set up properly. I integrated it with the monitoring system I wrote at work a while back to take some of the load off MySQL, and it’s worked exceptionally well.

While checking something else out in the monitoring system, I ran a report on the current Memcache status, and was kind of blown away. The system currently consists of 16 servers, 15 of which have memcached running on them, with 512MB allocated on each. That’s 7.5GB of cache memory, for those that don’t like doing math. I’ll let the report speak for itself…

192.168.0.2:11211
uptime: 563.945474537 days
read: 18097.7607219 GB
written: 19537.6376228 GB192.168.0.3:11211
uptime: 563.944502315 days
read: 18373.8532251 GB
written: 19785.8979402 GB

192.168.0.4:11211
uptime: 429.195578704 days
read: 13156.7254652 GB
written: 14532.1054876 GB

192.168.0.5:11211
uptime: 563.944247685 days
read: 19168.9044306 GB
written: 20775.6700451 GB

192.168.0.6:11211
uptime: 563.944212963 days
read: 18374.297407 GB
written: 19933.5923319 GB

192.168.0.7:11211
uptime: 563.944178241 days
read: 17361.7501419 GB
written: 18974.0357142 GB

192.168.0.8:11211
uptime: 563.942581019 days
read: 17525.4281332 GB
written: 18935.3812126 GB

192.168.0.9:11211
uptime: 317.73099537 days
read: 11330.5213323 GB
written: 12179.3746607 GB

192.168.0.10:11211
uptime: 0.774074074074 days
read: 3.608856056 GB
written: 5.957609009 GB

192.168.0.11:11211
uptime: 270.114976852 days
read: 9460.02688244 GB
written: 10477.9305441 GB

192.168.0.12:11211
uptime: 446.070590278 days
read: 14058.0880373 GB
written: 15349.2392257 GB

192.168.0.13:11211
uptime: 433.269293981 days
read: 13117.9202484 GB
written: 14265.9189342 GB

192.168.0.14:11211
uptime: 288.806412037 days
read: 9547.86924515 GB
written: 10396.3484227 GB

192.168.0.15:11211
uptime: 98.0899074074 days
read: 3658.49374042 GB
written: 4026.71671353 GB

192.168.0.16:11211
uptime: 18.6412731481 days
read: 529.824877851 GB
written: 591.686248784 GB

uptime (total): 5686.35829861 days
bytes read (total): 183.765072745 TB
bytes written (total): 199.767492713 TB

In just the current running processes, there is over 15 years of combined uptime, with 9 memcached processes up for over a year… 183 terabytes of data read from the memcached processes and 199 terabytes written. That’s a lot of uptime and a lot of data! I’ve got a couple of crash-happy servers in the cluster too. Without those, the numbers would be higher.

For those wondering, the write number is higher than the read number because the latest snapshot data is stored into memcache for easy retrieval each time data is collected. The read numbers are part of the snapshot storage process as well, and would also be higher if there was more activity on the web interface.

roflateam

This is great too!

roflmalware

It has been a loooong time since I posted. Yes, I’m still alive (obviously). Hopefully posting funny malware emails will make me more chatty.

From: “Microsoft Corp.”
Subject: Security Update for OS Microsoft Windows

Dear Microsoft Customer,

Please notice that Microsoft company has recently issued a Security Update for OS Microsoft Windows. The update applies to the following OS versions: Microsoft Windows 98, Microsoft Windows 2000, Microsoft Windows Millenium, Microsoft Windows XP, Microsoft Windows Vista.

Please notice, that present update applies to high-priority updates category. In order to help protect your computer against security threats and performance problems, we strongly recommend you to install this update.

Since public distribution of this Update through the official website http://www.microsoft.com would have result in efficient creation of a malicious software, we made a decision to issue an experimental private version of an update for all Microsoft Windows OS users.

As your computer is set to receive notifications when new updates are available, you have received this notice.

In order to start the update, please follow the step-by-step instruction:
1. Run the file, that you have received along with this message.
2. Carefully follow all the instructions you see on the screen.

If nothing changes after you have run the file, probably in the settings of your OS you have an indication to run all the updates at a background routine. In that case, at this point the upgrade of your OS will be finished.

We apologize for any inconvenience this back order may be causing you.

Thank you,

Steve Lipner
Director of Security Assurance
Microsoft Corp.

—–BEGIN PGP SIGNATURE—–
Version: PGP 7.1

QFXAYS969TA31O5JMAY2HXRJL97ZU9H8S7R7T06KUL5FMCH935XH9439655S8WRAM
7KX3N7KP23AGJLBHGLTK40LUCU1FH69MWFAMR8I275I6RVNXIC3VLR33V0R3DS50D
IH14NVVSKW1DPMQT1Q1WY5U64HWYX2OD9YGL0KXDNJ4DBV1369IY59CSUJ5J51FF0
5JL35Y5TYJO7HR131N9KCE0UAP6HZUVV5BOZ32P5FRJF6WT8M8TO5U289VUEMVBJA
D7TIHY79A04NJ2M0TKS6309XROLDUOI8A7V==
—–END PGP SIGNATURE—–

Attached was the file “KB779778.exe”. Yah… I’m totally going to run that! I think my favorite part was the PGP signature. It’s probably encoded code that will send someone to nasty sites, or something similar. The sad thing is that this one will probably fool a lot of people who don’t know any better.

A notice to those that don’t know any better… If you get this email, don’t execute the attachment. It will do ugly things to your windows computer, in all likelihood.