Blog temporarily down: dasBlog Limitations

time to read 2 min | 303 words

Well, it looks like I have run into some limits with dasBlog.

I have over 2,000 posts, and close to 1,200 files in my content directory. It gets to the points that just opening the directory has a noticable delay.
Trying to run dasBlog currently takes roughly 100% of the CPU, and takes forever. This is on my machine, by the way, so it is single user only.

Trying that on the server apperantly killed it. 

Profiling it shows that the fault is probably with the template processor, AddParsedObject and InitializeMacro. That is about all the information that I managed to get from VS profiler, I am currently trying out dotTrace, to see if it can gives me a better idea about what is going on there.

Using dotTrace, the picture is much clearer, it looks like the cost is in iterating over all the past entries, you can take a look here for the details:
dasblog-perf.png

I removed all the entries from July 06 and backward, and this seems to bring the blog to a working state again. This is a temporary measure only. I am not willing to give up 2+ years of blogging. I have uploaded the dtc (dot trace snapshot) here, if anybody is interested in taking a look I can provide the full backup history, which put dasBlog through the grinder.

At the same time, I am investigating Subtext, which may be more appropriate for my kind of blog. The main concerns are not breaking links (but it is acceptable to have redirect) and having to re-do the blog design.