During business hours:
I work from home a lot, so during business hours business protocols take priority
- HTTP/HTTPS
- Email
- IPSec
- SSH
- Skype
- MSN
- YIM
Yes, I use IM clients to keep up to speed with some of my clients. During this time things like torrents and news servers and large HTTP sessions (over 10MB) can be shaped back quite severely. This would mean I don't have to shape them back myself.
Evenings, and weekends during the day:
In the evenings (6/7 pm - 10pm) I mostly either game, browse the net or download stuff. I'd say prioritise gaming first, then downloads second if there's spare capacity for it. HTTP is definitely important.
Nights:
At night (10pm - 6/7am) I would like to have my downloads run full steam, if I have anything queued.
Totals and thresholds:
I know you are against caps. but perhaps an idea is to keep a running tally, not of total traffic, but of certain types of traffic (news servers, torrents, huge HTTP files). Once a certain soft threshold have been reached, these types of traffic are throttled back somewhat. This will stop someone from completely hogging the links 24/7.
As an example (this will need refining), let's look at the 256kbps package.
There are 86400s in a day. So at 32kB/s you can transfer 2764800 kB in a day, or just a tad under 2.5 GB. Over the course of 30 days, you would transfer 79.1 GB at max line usage. I would suggest setting a soft threshold at 1/2 of that, or 40 GB.
The above would then be proportionally larger for larger accounts, e.g. 80 GB for a 512 kbps.
I would go for this too.