| 3:32 pm on Mar 23, 2011 (gmt 0)|
you need to look at your log files as a starting point, do you have access to them through your host?
| 3:49 pm on Mar 23, 2011 (gmt 0)|
Looking at the 23rd March logs, I can see Demonoid referenced a lot - seems someone is using one of the avatars on the site in their profile. Could that be the cause, or would that be quite minimal?
I'm on cPanel, so presumably can see more info?
| 4:25 pm on Mar 23, 2011 (gmt 0)|
i don't know about cPanel i'm afraid.
but doing the maths, hot linking can be an issue.
say an avatar is 50k, then 20 calls is a Meg
20,000 is a Gig.
although seems a lot of page calls to me to get to 13.4 gigs
maybe you want to see if traffic spiked one day for some reason.
do you have a stats package included with your hosting?
| 4:39 pm on Mar 23, 2011 (gmt 0)|
I've seen Avatars get really big, file size wise. I've even seen it happen on Twitter every now and then. People will upload images that are huge to begin with. Then, due to some oddball dimensions, the image optimization routine gets whacked and you end up with a 50x50 "forced" size avatar that is actually 1024x768 and weighs in at 300k+. Those types of hotlinks will definitely wreak havoc on your bandwidth consumption.
| 5:52 pm on Mar 23, 2011 (gmt 0)|
Thanks for the replies. I'm going to try blocking the hotlinking with htaccess and see where that gets me - cpanel nor looking at the raw logs shows me more than a days activity at once (is that normal?)
| 7:53 pm on Mar 23, 2011 (gmt 0)|
usually cpanel includes a stats feature or two.
see if there is a button for awstats or webalizer. both should have multi-day traffic results.
also, see if cpanel has a hotling feature where it can (easily) be turned off.
| 12:52 am on Apr 15, 2011 (gmt 0)|
Webalizer will give you an ordered list by bandwidth. Recompress the avatar, add a line in .htaccess to redirect external requests to an off-site image and repeat. Stop when you get below a size that has bandwidth usage similar to the remaining ones.
| 5:52 am on Apr 15, 2011 (gmt 0)|
Thanks Hoople - it was a hotlinking problem it seems, so the htaccess trick to an offsite image worked.