Great .. I don't have any numbers.. but basically there is quite
little latency using the FTP interface, data is streamed in and out of
mysql on the fly, inserting and selecting blocks of rows..   The FTP
server is written in java using JDBC to talk the database, so it's
quite fast.



On Tue, 28 Sep 2004 10:57:09 -0700, Ed Lazor <[EMAIL PROTECTED]> wrote:
> Thanks for the article.  I'll check it out.
> 
> Throughput of 4600K/s is great.  How's latency?
> 
> -Ed
> 
> 
> 
> 
> > -----Original Message-----
> > So if the image was say 200K in size, the metadata for the image would
> > be 1 row in a table, and the image data would be 4 rows in the data
> > table.  3 full 64K rows + 1 partially used rows.
> >
> > There is a good article/sample code here on the kind of technique we
> > started with:
> > http://php.dreamwerx.net/forums/viewtopic.php?t=6
> >
> > Using chunked data, apache/php only needs to pull row by row(64k) and
> > deliver to the client, keeping the resultset size low = memory
> > overhead low.
> >
> > The storage servers (mysql storage) I have tested on the LAN; them
> > storing and retreiving data from mysql (using FTP gateway) at rates of
> > 4600K/sec.. which is I think the fastest speed my laptop network card
> > could deliver.
> >
> > That's pretty fast..  Rare day when most internet users can talk to
> > servers at those speeds.
> 
>

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to