From: Rebecca S. K. <reb...@em...> - 2007-03-28 20:40:02
|
We discovered recently that Fez has a fairly severe file-size limitation... The foxml class that constructs the Fedora object seems to be loading the binary file into memory (possibly several times?). In our tests, the limit was about a 24MB data upload for a server configured with 256MB of memory allotted for PHP. Is this a known problem? Have any other people run into this? Is there something in our configuration that might be causing this? It's not clear to me why a binary file would need to be loaded into memory at all, since it should be possible to add it to Fedora by referencing the uploaded file directly.=20 On a related note, is there any kind of bug-tracker for Fez? It looks like the one on SourceForge is not used, but it would be very helpful to have something-- especially as the user and developer bases grow. --=20 Rebecca Sutton Koeser, Ph.D. reb...@em... 404-712-2504 |
From: Matthew S. <yo....@gm...> - 2007-03-29 00:40:30
|
Hi Rebecca, I've noticed that it is a problem but we haven't had too many big files to make it an issue for us. When we start ingesting astronomy data it will become more of an issue. A solution I've thought of (at least on the eserve.php) side is to let eserve.php check the permissions and then use proxying to serve the content straight from fedora. So we'd need a way for eserve to open the proxy up for the datastream for the IP address of the user. On the ingesting side, the file needs to have it's JHOVE data read and maybe a thumbnail or two generated and I think if the filename has spaces, then we copy it to the temp directory with a different name so that we can get jhove to look at it. I haven't been able to find a way to stop curl from loading the file into memory both when posting it to fedora and when getting it back from fedora. Which is why I was thinking about proxying. It makes sense to get fedora to retrieve the file from the fez server using apache proxying perhaps or just expose an URL to fedora and move the files to that location. I think PHP could do that without loading the file into memory. Matt On 3/29/07, Rebecca Sutton Koeser <reb...@em...> wrote: > We discovered recently that Fez has a fairly severe file-size > limitation... The foxml class that constructs the Fedora object seems > to be loading the binary file into memory (possibly several times?). > In our tests, the limit was about a 24MB data upload for a server > configured with 256MB of memory allotted for PHP. > > Is this a known problem? Have any other people run into this? Is > there something in our configuration that might be causing this? > > It's not clear to me why a binary file would need to be loaded into > memory at all, since it should be possible to add it to Fedora by > referencing the uploaded file directly. > > > On a related note, is there any kind of bug-tracker for Fez? It looks > like the one on SourceForge is not used, but it would be very helpful > to have something-- especially as the user and developer bases grow. > > > -- > Rebecca Sutton Koeser, Ph.D. > reb...@em... > 404-712-2504 > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.5 (GNU/Linux) > > iD8DBQFGCtKa2wP7Byh4FYsRAq+HAJ0eFoAhIiak2R3bO70mhkRSiuqIhwCfS1O6 > zb+JlJjSCLb4nJCdab+dRXI= > =SaxC > -----END PGP SIGNATURE----- > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Fez-developers mailing list > Fez...@li... > https://lists.sourceforge.net/lists/listinfo/fez-developers > > |