Re: Catalogue system? there was : Mysql compress text field?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



    Hi!,

    Do you have other ideas about how do it?

    I thinking do :

    1. Save the report in a
YYYYMMDD/<name-of-report>/<name-of-report.num-page> tree directory
structure.
    2. Save in the database the information about the report, and the path
to the page directory.
    3. When the user request a report I go to the path and open the
name-of-report.00000 (the first page).

    Other information :

    . There are 2.002 reports montly (so under YYYYMMDD directory I have
2002 entries).
    . There are 210.000 pages montly.
    . The bigest report have 45.217 pages (so under <name-of-report>
directory I have in the worse case 45.217 entries).
    . The smallest report have 16 pages (so under <name-of-report> directory
I have in the best case 16 entries).
    . The average pages report is 7213 by day.

     I have the next dudes (I hope you can help me, or tell me where I can
go) :

    . The Linux filesystem support that number of files without degrading
the performance?
    . Any knows if exist something similar, or how i can search this under
what concept.....
    . Any other ideas to implement this?
    . For the moment i forgot the idea about zip the files.... I talk with
my boss and get more disk... :-)

pd.: sorry about the size of the mail.... i try to be more cleary possible.

Regards,
Patricio.

----- Original Message -----
From: "1LT John W. Holmes" <holmes072000@charter.net>
To: "Patricio Vera S." <pato_php_work@yahoo.es>; <php-db@lists.php.net>
Sent: Tuesday, March 04, 2003 2:45 PM
Subject: Re:  Mysql compress text field?


> >     I have a new project where i need show pages of report on demmand.
> That
> > reports are created in the batch process, and the whole file size is
about
> 5
> > Gb. (thats includes all the reports in a month, I need save about 12
> month).
> >
> >     I think in two alternatives :
> >
> >     1. I save the links in a mysql database, but the files are
compressed
> > (in zip format) in several directories, one directorie by day, so when
the
> > user request one report, I query the database, go to the path,
decompress
> > the file and return to the user.
>
> Use this method.
>
> >     2. I save the reports on the mysql database, so when the user
request
> > one report, I query the database and return the report. But if MySql
don't
> > compress the text field, that way is not practicable (HDD is limited).
>
> You'd have to zip the files, then read the data to insert into the table.
> Then, to retrieve, you'd have to select the data out, write it to a file
and
> unzip it before you sent it to the user. (According to your remarks)
Sounds
> like a lot of wasted time to me.
>
> ---John Holmes...
>
>
> --
> PHP Database Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php

___________________________________________________
Yahoo! Móviles
Personaliza tu móvil con tu logo y melodía favorito 
en http://moviles.yahoo.es

-- 
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php


[Index of Archives]     [PHP Home]     [PHP Users]     [Postgresql Discussion]     [Kernel Newbies]     [Postgresql]     [Yosemite News]

  Powered by Linux