Lotus Nut

In order to patch the guest and host servers with the newest critical Windows patch, we will have some brief downtime for all of the BleedYellow components tonight (that also includes Sametime...) This will occur sometime around 9PM Eastern.

Thanks!

In response to: What is your typical database maintenance routine?

Regarding Compact, I had an entry I posted a while back related to fragmentation and compacting. In that, I actually recommended using something like a load compact -c +10. We all know that fragmentation causes very poor performance. However, defragging causes the databases to be even more fragmented because every new write will likely be to a non-contiguous block on the drive. I've been pondering this a lot more lately and thinking that allowing the 10% white space (like you mentioned) is actually a good idea. Something could even be accomplished by some code to add data to a database and then delete it so that there's white space. Then defragmenting that database (using something like defraggler, you can choose to just defrag a single file at a time) will yield a contiguous space that will not become fragmented very quickly. This, coupled with archiving, I believe can be a pretty good boost in i/o performance. I'm cross-posting this comment at my blog too for further thoughts...

Yeah, David beat me to it! I think there were a lot of concerns with previous versions related to DB integrity. So we still see a good many customers still running fixups fairly regularly (more than once per week). I don't guess this would hurt, but it would definitely cause a good bit of overhead for something that's pretty unnecessary.

During the evening of Saturday, August 9, 2008 we will have some scheduled downtime for maintenance of all BleedYellow services.

 

Also, Sametime shouldn't be down for very long.

 

Thank you for your patience...

 

Cross-posted at BleedYellow Site Feedback