I really should post more often, as then I won’t have to cram to much topics into a single post. Anyway, some news: the “new” server I was talking about in previous posts has been performing well and seems to be able to much better handle the load, even at full 100mbps (10MB/sec) speeds. That it is reaching these speeds meant one other thing though: yet another server was needed to balance the growing need for more bandwidth. The new server has been delivered, but it’ll take some time to setup properly. Expect it to go live later this month.

I’ve also fixed a rather major bug in the bandwidth limit rules, or rather the data the bandwidth limits act upon. If you upload a file to ImageHost.org, it has a hourly bandwidth limit of 300MB per hour. If it goes over this limit in a single hour, the file is deleted. This limit however only applies if you are hotlinking to the file: if you properly use thumbnails or text links to link back to ImageHost.org, the file is not subject to this limit and could potentially use much more bandwidth: even gigabytes of bandwidth per hour is allowed that way.

There was however a problem with the logic my scripts used to determine if a file is solely being hotlinked to, or if thumbnails or text links are used to link to it. I won’t go into details, but basically the logic only worked properly for data collected earlier, not for data collected in the past hour. So if a large new file (say a 100MB ZIP file) was uploaded an downloaded a few times (3-4 times or more), it would go over the 300MB hourly limit. However because the “hotlinking logic” was not working, the file would get deleted by the bandwidth limit script – even if you had properly used text links to link to the file. Fortunately this problem has now been fixed.

This entry was posted on Tuesday, November 4th, 2008 at 10:26 and is filed under News. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.