Program crash

[peterlaursen]

Selecting “view data” form a table displays the first 1000 rows (“limit 0,1000”). Checking the checkbox “Show All” displays all rows. So far so good. But an attempt to UNCHECK the checkbox makes the program hang – or rather it does not really hang but starts working like mad (>90% CPU-resources) but nothing happens. You will have to close the program,

[CalEvans]

I've not experienced this problem. The only time it hangs for long periods of time is when I uncheck that box on one of my large (100,000+ rows) tables with 3 memo fields. (I know…bad design). Since it's hauling this data over the net, it takes a while and the background processing seems to not work in this situation.

Could it be that it's not hung in your case but simply trying to suck all the data in and build the grid?

=C=

[peterlaursen]

You got a point … I tested with a small base with a few hundred rows, and there is now problem.

But why must it take 50 or 100 times as much time (or more) to display 1000 rows the second time compared to the first time ?!

The code must be ineffective the second tme!

I experience the problem with two tables with respective 17000 and 37000 rows (both with some BLOBs in them) . But it's not the number of rows (I have another with also about 17000 rows, with only an integer-PK, a timestamp and one more number. Here is no problem).

But now I waited for about 10 minutes and the 17000-row table came back to the screen! The 37000-row table won't do in 20 minutes (and memory consumption keeps rising)- and that's with a DB on localhost. But I don't think the host matters here – the program calculates; it doesn't send or receive data. Table size (MYD-file) is about 8 MB and that's not a lot … There is an integer PK, so it should not have difficulty in sorting and filtering. And memory consumption keeps on rising. why must the program use +200 MB memory (physical + virtual) to work with 8 MB of data … ??

The use of resources (CPU + memory) by the MySQL server is completely normal … the problem is with SQLyog!

[Ritesh]

peterlaursen wrote on May 21 2005, 12:55 AM:

Selecting “view data” form a table displays the first 1000 rows (“limit 0,1000”). Checking the checkbox “Show All” displays all rows. So far so good. But an attempt to UNCHECK the checkbox makes the program hang – or rather it does not really hang but starts working like mad (>90% CPU-resources) but nothing happens. You will have to close the program,

This is a known performance issue with SQLyog and we plan to fix it in v4.1.

[Author]

Posts