extra-sized memory/time consuming scripts

[jlive]

I developed many php scripts all working in the usual memory and time limit (8Mb, 30secs).
Only one script, the indexing one, is more expensive.

Now I'm working in two directions:
1) extend the limits (php.ini)
2) split the indexing script in more single-step cascading scripts

[1] The first solution makes my scripts working only on robust servers. This could be a strong limit in the code distribution.

[2] It's working this way: all the single-step script do not flush anything to the client, and have at the end an header statement redirecting to the next-step script. They all write some log note into a file. The last-step script performs the task to read the file and flush it to the client.

Here there's something not working:
Each single-step script write into the file, but the next find the file empty.

Any comment is appreciated, both on the choice (1) or (2) or something else, and on the problem about (2).

Thank you.

[LordShryku]

Well, if you own the server and/or have the option of messing with the php.ini file, I'd definately go with #1. Saying that it will take a "more robust server" is not entirely true. Any server with only 8M of memory to spare for PHP should be put to death anyway. On the same note, if you only wanted to do it for this script, you could just use [man]ini_set[/man] at runtime to configure what's needed for this script to run.

[jlive]

Thank you, my Lord

[jlive]

As my provider let large freedom in setting the configuration, and following the suggestion of LordShryku, I finally choosed to extend the memory_limit and max_execution_time in my php.ini.

memory_limit = 64
output_buffering = Off
max_execution_time = 60

But my script still abort. The most critical task, that most memory consuming, fails after around 10secs.

I tried to monitor the memory usage, but the function get_memory_usage() is not defined (I know php has to be rebuilt with a particular option to let using that, but this is out of my control).

Btw my feeling is that the 64-memory limit is not the cause of the failure.

I get NO other message than 500 Internal Server Error.

My setting in php.ini about error messaging are:

display_errors = On
display_startup_errors = On
error_reporting = E_ALL & ~E_NOTICE
log_errors = On

Can that kind of failure make no error message flushed in output ?

In my php.ini:

implicit_flush = Off

Btw, also if On, no message is flushed to the output before the failure.

Help! please

[Moonglobe]

memory_limit = 64 means 64 BYTES. you want "memory_limit = 64M"

[jlive]

Now 64M. No change. Abort at the same point.

Suppose 'M' is optional ....with 64 bytes-memory probably process a couple of lines of code then abort immediately, or not ?

... or this is another proof that's not a matter of memory...

So again, how can get more info about that error ?

[Moonglobe]

i know one site that does it as well, but i have no idea why ... sorry, never experienced it m'self

[jlive]

I know some other too. Btw this does not make me feeling better...

thanks moon

[BuzzLY]

Please do not post such threads in this forum. Code Critique is for critique of completed code. Moving to General Help.

[jlive]

ops, sorry buzzly
at the beginning seemed a matter of which approach is better
btw it's my mistake
thank you for the shift

[BuzzLY]

No worries mate... 🙂