Alaska Software Inc. - Thread problem with not releasing Ram Memory
Username: Password:
AuthorTopic: Thread problem with not releasing Ram Memory
Nolberto Paulino EsterellThread problem with not releasing Ram Memory
on Tue, 13 Jul 2010 17:14:28 -0400
Hi Group

The problem I have when I use DBF large with over 600 thousand records
April at the Time of the DBF take long, and when I insert a record Also New

When I navigate in the Browse, sometimes it takes a lot, This makes both
in RED with locally

Roger, you could tell me the steps to follow in order to accelerate Reading
and recording process and that this is not so slow, and with regard to how I
can improve browse pagination to be faster in the use of filtering.

I Loaded the Task Manager and I've noticed that whenever I go to each module
of the application Process is constantly increasing

First entry into the Task Manager process to PV.EXE with 24.584 KB the Load
Point of Sale Module Expands to 29.688 KB, I leave and enter another Once 
the
POS module and Increase to 29.720 KB

Now I leave the system
When I go back to the Point of Sale Module Shoot This is 47.352 KB
and sientra the Client Module Increases to 53.860 KB

When I call each module _ActiveDLL use this function ("(|o|pvpu01 (oDlg: 
drawingarea)) ")

FUNCTION _ActiveDLL (bblock)
return (| o | o: = Thread (): new () or: Start (& (bblock)))

and when I leave the mudulo threadobject use this code (): quit ()

Now you can tell me please what would be my solution
This is urgent I

The terminal is like this P4 1G RAM each.


Nolberto Paulino
Regards
AUGE_OHRRe: Thread problem with not releasing Ram Memory
on Wed, 14 Jul 2010 15:21:01 +0200
hi,

> When I call each module _ActiveDLL use this function ("(|o|pvpu01 (oDlg: 
> drawingarea)) ")
>
> FUNCTION _ActiveDLL (bblock)
> return (| o | o: = Thread (): new () or: Start (& (bblock)))
>
> and when I leave the mudulo threadobject use this code (): quit ()

:quit() does not "release" any Thread ... it just stop processing Code
your Thread Object is still alive and "eat" your RAM

to "release" a Thread Object you need

oThread:setInterval(NIL)
oThread := NIL

greetings by OHR
Jimmy
James Loughner Re: Thread problem with not releasing Ram Memory
on Wed, 14 Jul 2010 11:13:54 -0400
Filters are just slow. They must skip over any record that does not meet
the criteria. So it still must fetch the record across the network
whether or not it gets displayed. So depending on the filter you can be
fetching and rejecting thousands of records for each record displayed.

Scopes are much much faster but then you must have an appropriate index
available to set the scope against. Thus it limits the flexibility you
can give to the client. You can combine scopes and filters but always
set the scope first to limit the number of records that require filtering.

Jim

On 07/13/2010 05:14 PM, Nolberto Paulino Esterell wrote:
> Hi Group
> 
> The problem I have when I use DBF large with over 600 thousand records
> April at the Time of the DBF take long, and when I insert a record Also New
> 
> When I navigate in the Browse, sometimes it takes a lot, This makes both
> in RED with locally
> 
> Roger, you could tell me the steps to follow in order to accelerate Reading
> and recording process and that this is not so slow, and with regard to
> how I
> can improve browse pagination to be faster in the use of filtering.
> 
> I Loaded the Task Manager and I've noticed that whenever I go to each
> module
> of the application Process is constantly increasing
> 
> First entry into the Task Manager process to PV.EXE with 24.584 KB the Load
> Point of Sale Module Expands to 29.688 KB, I leave and enter another
> Once the
> POS module and Increase to 29.720 KB
> 
> Now I leave the system
> When I go back to the Point of Sale Module Shoot This is 47.352 KB
> and sientra the Client Module Increases to 53.860 KB
> 
> When I call each module _ActiveDLL use this function ("(|o|pvpu01 (oDlg:
> drawingarea)) ")
> 
> FUNCTION _ActiveDLL (bblock)
> return (| o | o: = Thread (): new () or: Start (& (bblock)))
> 
> and when I leave the mudulo threadobject use this code (): quit ()
> 
> Now you can tell me please what would be my solution
> This is urgent I
> 
> The terminal is like this P4 1G RAM each.
> 
> 
> Nolberto Paulino
> Regards