Stores a file on the FTP server (non-blocking)
(PHP 4 >= 4.3.0, PHP 5)
Example 737. ftp_nb_put() example
Example 738. Resuming an upload with ftp_nb_put()
Code Examples / Notes » ftp_nb_put
When using non blocking functions if you try to disconnect while your non blocking operation is in progress the disconnect command will not work until the operation is not finished.
If you receive an error like:
Warning: ftp_nb_put(): Unable to service PORT commands in /path/to/file.php on line 27
verify whether you need to be in PASV mode. You can go into PASV mode by declaring
brandon dot farber
I couldn't see this noted anywhere...
ftp_nb_put apparently takes a much much longer time to upload the file than ftp_put (I haven't done any packet sniffing or logging tests to find out why). I was using a script, nearly identical to the example above, and a 100KB file had only uploaded 3.99KB after about 8 minutes! The php script naturally timed out before it was complete.
I changed my function to use ftp_put, got rid of the loop to check FTP_MOREDATA (as you will see in the example above), and the same script uploaded 2.2MB within 30 seconds with no other changes.
If you're using this function instead of ftp_put *purely to try to speed up your script* and it's taking a long time, you might want to try ftp_put instead.
I tried to use both ftp_put() and ftp_nb_put() adding the
variable $start = date("Y:m:d h:i:s"); at the begin of the script and the variable $end = date("Y:m:d h:i:s"); at its end, after the file upload function.
With the gprs connection I'm now using and trying to upload a .jpg file of 67,5 kb the time difference between $start and $end was 40 seconds in both cases, so I can suppose that there is no difference between these upload function.
The difference comes if you put anything inside the while ($ftp_upload == FTP_MOREDATA) loop.
I hope this note can help.
Don't add a sleep() inside the loop. If you do you will severely slow down the upload.
In my tests, each time through the loop it send about 2.5K, looping about 220 times per second. (Which is very little.)
You won't necessarily get the same numbers as me per loop, but clearly PHP does it's own management of the loop so that you don't consume all the CPU on the server.