while loops within while loops causing huge memory problem

[monomaniac21]

hi all

i have a script that retrieves rows from a single table, rows are
related to eachother and are retrieved by doing a series of while loops
within while loops. bcos each row contains a text field they are fairly
large. the net result is that when 60 or so results are reitreved the
page size is 400kb! which takes too long to load. is there a way of
shorterning this? freeing up the memory say, bcos what is actually
displayed is not that much, its just the use of multiple loops (about
10) that does it i think

[Moot]

Re: while loops within while loops causing huge memory problem


monomaniac21 wrote:

hi all
>
i have a script that retrieves rows from a single table, rows are
related to eachother and are retrieved by doing a series of while loops
within while loops. bcos each row contains a text field they are fairly
large. the net result is that when 60 or so results are reitreved the
page size is 400kb! which takes too long to load. is there a way of
shorterning this? freeing up the memory say, bcos what is actually
displayed is not that much, its just the use of multiple loops (about
10) that does it i think

If the page size delivered to the browser is 400kb, then it's 400kb's
worth of data. You can't change that by freeing up memory in PHP.

If the page is getting too large, then consider using pagination to
break up all that data into smaller sets across multiple pages. For
instance, limit each page to only show 100 records and provide
Previous/Next links to navigate across all the results.

Moot

[Kimmo Laine]

Re: while loops within while loops causing huge memory problem

"monomaniac 21" <mcyi2mr3@googl email.comwrote in message
news:1161195237 .493677.322990@ e3g2000cwe.goog legroups.com...

hi all
>
i have a script that retrieves rows from a single table, rows are
related to eachother and are retrieved by doing a series of while loops
within while loops. bcos each row contains a text field they are fairly
large. the net result is that when 60 or so results are reitreved the
page size is 400kb! which takes too long to load. is there a way of
shorterning this? freeing up the memory say, bcos what is actually
displayed is not that much, its just the use of multiple loops (about
10) that does it i think

Clearly the code needs to be optimized. Depending how bad the design is, you
should start looking at the query string, maybe the database structure. Now
it just doesn't sound too smart if it takes ten nested while loops to pull
out some simple data... But without seeing the actual code it's very
difficult to say anything more specific.

--
"Ohjelmoija on organismi joka muuttaa kofeiinia koodiksi" - lpk
http://outolempi.net/ahdistus/ - Satunnaisesti päivittyvä nettisarjis
spam@outolempi. net | rot13(xvzzb@bhg byrzcv.arg)

[Rik]

Re: while loops within while loops causing huge memory problem

Kimmo Laine wrote:

"monomaniac 21" <mcyi2mr3@googl email.comwrote in message
news:1161195237 .493677.322990@ e3g2000cwe.goog legroups.com...

>hi all
>>
>i have a script that retrieves rows from a single table, rows are
>related to eachother and are retrieved by doing a series of while
>loops within while loops. bcos each row contains a text field they
>are fairly large. the net result is that when 60 or so results are
>reitreved the page size is 400kb! which takes too long to load. is
>there a way of shorterning this? freeing up the memory say, bcos
>what is actually displayed is not that much, its just the use of
>multiple loops (about 10) that does it i think

>
>
Clearly the code needs to be optimized. Depending how bad the design
is, you should start looking at the query string, maybe the database
structure. Now it just doesn't sound too smart if it takes ten nested
while loops to pull out some simple data... But without seeing the
actual code it's very difficult to say anything more specific.

A self-referential table of a adjacency model often takes either a lot of
while loops or a lot of joins. It might be usefull to switch to a nested
model in that case.

http://dev.mysql.com/tech-resources/articles/hierarchical-data.html

Neither explains a 400KB HTML page offcourse, if the actual data is small,
something else is definately wrong.

Grtz,
--
Rik Wasmus