Open GoogleCodeExporter opened 9 years ago
After tons of other memory workups, I came up with the following. I originally
ran
the sourceforge class and everyone knows now that there's 2 main issues (1)
corrupt
example .xls and (2) wrong include name in reader.php. Any programmer should
pick
those up quickly. I fixed those without reading any forums or help and I had it
up
and running and dumping tons of excel data to mysql. Of course, I was on a
brandnew,
powerful quad-proc 3+gigs of ram system running vista, apache, php, and mysql.
So,
when I had to work on a refurbed piece of crap I installed AppServ thinking I
could
use the php I wrote for the other system to get the local excel files in mysql.
The
original OLEread ran into tons of problems. Then, I found Mr Kruse's updated
class
and I got better performance right off. Plus I could already see tons of better
code
in the class with extra parameter calls. However, as stated above my excel
folder was
only going to about 90% completion before FATAL ERROR with memory allocation. I
did
everything as mentioned above plus changed memory allocation in my Windows_sys
ie
took away from programs and gave to cache and vice-versa. I was just looking at
installing memcache (PECL or xcache,etc) today when I noticed my AppServ had
two
instances running of httpd at about 15k mem usage a piece. So, to the point....
If
you're having memory problems with the php class then your problem may lay with
apache which is a huge memory hog. I downloaded lightTPD for windows. A small
executable, although, in hungarian (couldn't find the english windows exe) I
was up
and running a WLMP in about 60 seconds. I made a phpmyadmin folder in my HTDOCS
folder, made a shortcut to my index.php (of course username is root and no
password
to begin with). I copied over my files and ran my script to completion with
about 27k
(2 httpd instances at 15k = 30k) less mem usage. LightTPD runs between 3k-5k
mem
usage. Again excellent php class just problematic on systems that can't sport
apache
and access tons of xls files or lines. Hope this helps someone that's getting
memory
usage errors of any kind. Focker out.
Original comment by charlier...@gmail.com
on 12 Oct 2009 at 9:27
Original issue reported on code.google.com by
charlier...@gmail.com
on 9 Oct 2009 at 9:20