Re: mySQL 3.23.32 memory optimization ....

job, and if you consider this approach convenient. -- Marcello Giovagnoli R D Logical System S.r.l. 23, Via R. Scotellaro I-60035 Jesi (AN) -ITALY Tel/Fax: +39 731 200374/200378 mailto:[EMAIL PROTECTED] http://www.logicalsystem.it

mySQL 3.23.32 memory optimization ....

as SQL_CURSOR_FORWARD_ONLY, of course. Anyway, if there is another method to save memory, please let me know how I can do it, without change my code (if it is possible). Regards marcello marcello giovagnoli Logical System s.r.l. Via Rocco Scotellaro 23 60035

Re: mySQL 3.23.32 memory optimization ....

Hi Monty, Why do you need to retrieve so many rows to the client? Can't you use LIMIT to restrict the number of result rows? The point is that the program scans the entire table and process each row in a diffrent way, executing other queryes inside the main SQLFetch() loop. Someting like

To thread or not to thread this is the question ..........

moving on the fly libpthread-0.9.so from RedHat to Slackware (the system is up and there are 102 users connected !!!). Could someone help me ? Thanks in advance. marcello - marcello giovagnoli Logical System s.r.l. Via Rocco Scotellaro 23 60035

Slackware AND mySQL 3.23.32 memory problems ....

Hi, I'm sorry, for my previus question "To thread or not to thread " but now all it's OK. :) Looking at /etc/my.cnf, i could see two variables: set-variable= thread_cache=8 set-variable= thread_concurrency=8 # Try number of CPU's*2 this should set the edge to the maximum