This link has been bookmarked by 68 people . It was first bookmarked on 21 Jul 2006, by prasad chalasani.
-
15 Jan 09
-
02 Oct 08
-
16 Sep 08
-
11 Jul 08
-
10 Mar 08
-
28 Feb 08
-
22 Feb 08
-
07 Feb 08
-
05 Feb 08
-
08 Jan 08
-
18 Dec 07
-
16 Dec 07
-
25 Oct 07
-
20 Sep 07
-
29 May 07
-
08 May 07
-
25 Apr 07
-
29 Mar 07
-
15 Mar 07
-
07 Mar 07
-
09 Feb 07
-
04 Feb 07
-
16 Jan 07
-
12 Dec 06
-
27 Nov 06
-
04 Nov 06
-
17 Sep 06
-
05 Sep 06
-
25 Aug 06
-
03 Aug 06
-
02 Aug 06
-
26 Jul 06
-
02 May 06
-
21 Apr 06
jeanjordaanThe solution hit me the other day -- I can just use Amazon's new Amazon S3 data-storage service to host chicagocrime.org's media files, so my own Apache server can focus on serving dynamic pages. S3 is very cheap -- 15 cents a month for each gig of storag
-
20 Apr 06
-
18 Apr 06
-
10 Apr 06
-
The solution hit me the other day -- I can just use Amazon's new Amazon S3 data-storage service to host chicagocrime.org's media files, so my own Apache server can focus on serving dynamic pages. S3 is very cheap -- 15 cents a month for each gig of storage (and I have only 936 K of media files) and 20 cents per gig bandwidth. That's peanuts.
-
-
-
How I'm using Amazon S3 to serve media files As traffic to chicagocrime.org has steadily increased, I've been looking for ways to tweak the site's performance. The site runs on a rented dedicated server with Apache/mod_python, PostgreSQL and Django. (I'd love to bite the bullet and buy proper servers but haven't done so yet. Donations are welcome!) One thing that's always bugged me is that chicagocrime.org's Apache instance serves both the dynamic, Django-powered pages and static media files such as the CSS and images. It's inefficient for a single Apache instance to act as both an application server (mod_python) and a media server. A bunch of Apache configuration tweaks can improve performance of one aspect of serving but are somewhat detrimental to the other aspect. For example, using the KeepAlive directive improves Apache's media-serving capabilities, but KeepAlive is detrimental in a server arrangement that mainly churns out dynamic pages. So if a single Apache instance does both media serving and dynamic page creation, you can't optimize for both cases. (When I worked at LJWorld.com, we had the luxury of separate application, media and database servers, and we have a similar setup where I work now, but I can't afford separate servers for my little side projects.) The solution hit me the other day -- I can just use Amazon's new Amazon S3 data-storage service to host chicagocrime.org's media files, so my own Apache server can focus on serving dynamic pages. S3 is very cheap -- 15 cents a month for each gig of storage (and I have only 936 K of media files) and 20 cents per gig bandwidth. That's peanuts. It was easy to get this working; took less than an hour total. Here's what I did: 1. First, I signed up for an Amazon S3 account. Do that by clicking "Sign Up For Web Service" on the main S3 page. When you sign up, you get two codes: an access key ID and secret access key. 2. Next, I created an S3 "bucket" for my chicagoc
-
-
-
How I'm using Amazon S3 to serve media files As traffic to chicagocrime.org has steadily increased, I've been looking for ways to tweak the site's performance. The site runs on a rented dedicated server with Apache/mod_python, PostgreSQL and Django. (I'd love to bite the bullet and buy proper servers but haven't done so yet. Donations are welcome!) One thing that's always bugged me is that chicagocrime.org's Apache instance serves both the dynamic, Django-powered pages and static media files such as the CSS and images. It's inefficient for a single Apache instance to act as both an application server (mod_python) and a media server. A bunch of Apache configuration tweaks can improve performance of one aspect of serving but are somewhat detrimental to the other aspect. For example, using the KeepAlive directive improves Apache's media-serving capabilities, but KeepAlive is detrimental in a server arrangement that mainly churns out dynamic pages. So if a single Apache instance does both media serving and dynamic page creation, you can't optimize for both cases. (When I worked at LJWorld.com, we had the luxury of separate application, media and database servers, and we have a similar setup where I work now, but I can't afford separate servers for my little side projects.) The solution hit me the other day -- I can just use Amazon's new Amazon S3 data-storage service to host chicagocrime.org's media files, so my own Apache server can focus on serving dynamic pages. S3 is very cheap -- 15 cents a month for each gig of storage (and I have only 936 K of media files) and 20 cents per gig bandwidth. That's peanuts. It was easy to get this working; took less than an hour total. Here's what I did: 1. First, I signed up for an Amazon S3 account. Do that by clicking "Sign Up For Web Service" on the main S3 page. When you sign up, you get two codes: an access key ID and secret access key. 2. Next, I created an S3 "bucket" for my chicagoc
-
-
08 Apr 06
gallox smithI can just use Amazon's new Amazon S3 data-storage service to host chicagocrime.org's media files, so my own Apache server can focus on serving dynamic pages.
-
-
Boris MannS3 is cheap...sort of. Main point is offloading servers from handling static files. We really need to fix the file API to do this out of the box.
-
07 Apr 06
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.