We have a user who wants to upload podcasts to her website via PHP forms
(Wordpress & Drupal). Some of the podcasts are in the 60-minute+ range
and take up over 100MB. Has anyone on the list had experience with this
sort of thing?

Our setup:
Dell PowerEdge 2400, 700MHz P3, 1.25 GB RAM, running stock Sarge
2.6.8-3-686 SMP kernel
Apache 1.3.33 (standard Sarge build)
PHP 4.3.10-18 (via suphp package), running as CGI

Thus far, I've modified the following php settings:

upload_max_size 250M
post_max_size 500M
memory_limit 500M
max_execution_time 3600

and the following Apache setting:
Timeout 3600

I had to modify Firefox as well, via about:config.

After all this mucking around, the file still took 20 minutes to
upload--over our LAN, no less! While the file was being written to the
upload_tmp_dir (/tmp), the php4 process gobbled over 100MB RAM. If this
only happened once a day, we might be able to live with it, but ten
concurrent uploads of this size would pretty much bring things to a
halt. How have you all handled this?

--John


--
To UNSUBSCRIBE, email to debian-isp-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Fri, 01 Dec 2006, John Miller wrote:
> We have a user who wants to upload podcasts to her website via PHP forms
> (Wordpress & Drupal). Some of the podcasts are in the 60-minute+ range
> and take up over 100MB. Has anyone on the list had experience with this
> sort of thing?

Yes. I have the same sort of problem.

> halt. How have you all handled this?

ftp accounts, and a separate "huge stuff goes here" URI space. The software
we use here allows the user to provide hyperlinks, so these large files are
kept outside the content management system.

--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh


--
To UNSUBSCRIBE, email to debian-isp-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

John Miller wrote:

> After all this mucking around, the file still took 20 minutes to
> upload--over our LAN, no less! While the file was being written to the
> upload_tmp_dir (/tmp), the php4 process gobbled over 100MB RAM. If this
> only happened once a day, we might be able to live with it, but ten
> concurrent uploads of this size would pretty much bring things to a
> halt. How have you all handled this?

We teach them how to use Efffff Teeee Peeee.

Nate


--
To UNSUBSCRIBE, email to debian-isp-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Fri, Dec 01, 2006 at 07:45:17PM -0500, John Miller wrote:
> We have a user who wants to upload podcasts to her website via PHP forms
> (Wordpress & Drupal). Some of the podcasts are in the 60-minute+ range
> and take up over 100MB. Has anyone on the list had experience with this
> sort of thing?

Not answering your question, but that's way too big. She needs to use
better compression (unless that happens on the server end).
--
Carl Fink nitpicking@nitpicking.com

Read my blog at nitpickingblog.blogspot.com. Reviews! Observations!
Stupid mistakes you can correct!


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

John Miller wrote:
> We have a user who wants to upload podcasts to her website via PHP forms
> (Wordpress & Drupal). Some of the podcasts are in the 60-minute+ range
> and take up over 100MB. Has anyone on the list had experience with this
> sort of thing?
>
> Our setup:
> Dell PowerEdge 2400, 700MHz P3, 1.25 GB RAM, running stock Sarge
> 2.6.8-3-686 SMP kernel
> Apache 1.3.33 (standard Sarge build)
> PHP 4.3.10-18 (via suphp package), running as CGI
>
> Thus far, I've modified the following php settings:
>
> upload_max_size 250M
> post_max_size 500M
> memory_limit 500M
> max_execution_time 3600
>
> and the following Apache setting:
> Timeout 3600
>
> I had to modify Firefox as well, via about:config.
>
> After all this mucking around, the file still took 20 minutes to
> upload--over our LAN, no less! While the file was being written to the
> upload_tmp_dir (/tmp), the php4 process gobbled over 100MB RAM. If this
> only happened once a day, we might be able to live with it, but ten
> concurrent uploads of this size would pretty much bring things to a
> halt. How have you all handled this?
>
> --John
>
>

You could use our Java upload applet her:

http://www.gplhost.com/software-jupload.html

It's open source.

Thomas


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Sat, Dec 02, 2006 at 02:12:54AM -0500, Carl Fink wrote:
> On Fri, Dec 01, 2006 at 07:45:17PM -0500, John Miller wrote:
> > We have a user who wants to upload podcasts to her website via PHP forms
> > (Wordpress & Drupal). Some of the podcasts are in the 60-minute+ range
> > and take up over 100MB. Has anyone on the list had experience with this
> > sort of thing?
>
> Not answering your question, but that's way too big. She needs to use
> better compression (unless that happens on the server end).

Does that work for podcast audio?

I do some audio work for my church and I digitally record the sermons at
the church, convert them to ogg and upload them. A 30 minute clip is
usually in the neighborhood of 8-10 MB. So, 100 MB for 60 minutes seems
ascessive, but i am not familiar with what format that is.

Regards,

-Roberto

--
Roberto C. Sanchez
http://people.connexer.com/~roberto
http://www.connexer.com

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFFcYgv5SXWIKfIlGQRAmsDAJ9X2TzPB29r/dTtywj9AGaxrfWuqQCdFRkX
rGwCu3XaJWwpHo8VTUN02kc=
=bPoH
-----END PGP SIGNATURE-----

Am 2006-12-01 19:45:17, schrieb John Miller:

> After all this mucking around, the file still took 20 minutes to
> upload--over our LAN, no less! While the file was being written to the
> upload_tmp_dir (/tmp), the php4 process gobbled over 100MB RAM. If this
> only happened once a day, we might be able to live with it, but ten
> concurrent uploads of this size would pretty much bring things to a
> halt. How have you all handled this?

Install at least 3 GByte Memory on the Machine :-)

Note: I have system which allow fileuploads too, but
it is a Dual-Opteron with 32 GByte of memory.

Thanks, Greetings and nice Day
Michelle Konzack
Systemadministrator
Tamay Dogan Network
Debian GNU/Linux Consultant


--
Linux-User #280138 with the Linux Counter, http://counter.li.org/
##################### Debian GNU/Linux Consultant #####################
Michelle Konzack Apt. 917 ICQ #328449886
50, rue de Soultz MSM LinuxMichi
0033/6/61925193 67100 Strasbourg/France IRC #Debian (irc.icq.com)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFFgB6cC0FPBMSS+BIRAuc4AJ9Jnjb8zNL4P3CMhO+LGn ZJ3DmMnQCeIHlU
/4rf4uebX8vqekKRLAYHVog=
=7xSt
-----END PGP SIGNATURE-----