By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,874 Members | 1,028 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,874 IT Pros & Developers. It's quick & easy.

while loops within while loops causing huge memory problem

P: n/a
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

Oct 18 '06 #1
Share this Question
Share on Google+
3 Replies


P: n/a

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

Oct 18 '06 #2

P: n/a
"monomaniac21" <mc******@googlemail.comwrote in message
news:11**********************@e3g2000cwe.googlegro ups.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
sp**@outolempi.net | rot13(xv***@bhgbyrzcv.arg)
Oct 19 '06 #3

P: n/a
Rik
Kimmo Laine wrote:
"monomaniac21" <mc******@googlemail.comwrote in message
news:11**********************@e3g2000cwe.googlegro ups.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/...ical-data.html

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

Grtz,
--
Rik Wasmus
Oct 19 '06 #4

This discussion thread is closed

Replies have been disabled for this discussion.