Anybody out there willing to share information of on the number of students using GAFE on a school site and the nature/bandwidth told the internet connection used to support it. Not looking for anything too technical just something like "we have X students and this type of connection works for us". If you have something geeky even better!
one plus one
Shared publicly•View activity
- Hi Clive, we are a small private school in Guatemala City, Guatemala (just a bit south of the border.)
We have 50 faculty who use the Internet - and our Google Apps account - continuously throughout the day.
We have roughly 200 students (only about 125 actually use the Internet.) Of those 125 students I'd say 35 to 40% of them are heavily on their Google account throughout the day.
We have 4.0 Mbit up and 4.0 Mbit down. With this usage we find the Internet is very slow and exhibits lags from time to time.Jul 26, 2014
- Using wireless: 200 students, 22 teachers, 4 admin, wireless access points in every classroom, in our quad area, in our Computer Lab and Day-Care, in our hall/gym, and our outside courts/play areas. 20 up and 20 down. Teachers have laptops, some have Google Chromecast, a couple have iPads, 12 chromeboxes and 200 chromebooks.Jul 26, 2014
- 800 students, 70 teachers, all (nearly) with 1:1 devices. Heavy users of GAFE plus other internet use. We have 100 Mbps coming in, and peak at about 70% couple of times a week. Average use during the day probably about 40% of that.Jul 27, 2014
- Thanks for the inputs.
Quite by chance it looks like I've picked up responses for each end of the spectrum plus one in the middle. The consensus looks like you should plan for about 150Kbps for each user which makes operating even very large schools over a 100Mbps link quite feasible as Richards post proves.
The robustest of the protocols is probably taken to the limit by Kenneth. The fact that that even works is quite amazing.Jul 29, 2014
- The Google Apps side of things is probably quite minor - the "file sizes" (which doesn't even make sense) going backwards and forwards are tiny and editing and sharing documents and presentations takes very little bandwidth. The killer is always video - uploading and downloading/watching videos. We don't have youtube blocked, and its used quite a lot in classes, so bear that in mind when thinking about bandwidth.Jul 29, 2014
- To add to what Richard Kelleher said: once you start having an entire class or two or three start making and uploading videos, you can get bogged down temporarily.Jul 29, 2014
- I think a design for a GAFE school needs to consider that fact. Of course it's the same problem for most schools but when the core service delivery is down the same line you can actually feel the pain. There might be a case for recalling the role of the 'cache server' that was popular when business operated from dial up modems and every byte was precious.
This wouldn't operate with a blanket approach, just target the heavy media sites using something like http://cachevideos.com. If the staff member knows that a media resource is going to hit multiple times this can all be served locally by preloading the cache. Without having any data I suspect a large amount of this data is the same video being downloaded multiple times as part of a class group exercise.
This is the key point of course. There's no point in caching something that only viewed once, which one reason why the idea died in business (along with the higher bandwidths). But schools are a different case.Jul 30, 2014