Smalltalk › Cincom › VisualWorks

Memory issues with GLORP and VWNC 7.7.1

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

6 messages Options

Alberto Bacchelli

Memory issues with GLORP and VWNC 7.7.1

Hi all,

Last month I moved to vwnc 7.7.1, after almost a couple of years in nc 7.6.
I use GLORP in my applications.
Before moving, I used to have no problem with memory.
Now, I often experience memory issues when dealing with GLORP.
In most of the cases, while I read objects stored in the db,
VW crashes with a out of memory message.

Did anything memory (or glorp) related change from 7.6 to 7.7.1?

Thank you in advance,

Cheers,
Alberto
_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

Niall Ross

Re: Memory issues with GLORP and VWNC 7.7.1

Dear Alberto,
couple of questions that will help memory-savvy VWers (of whom I am
not one) to help you.

1) Which DB are you using?

2) There were memory changes in VW7.7.1 - look at
.../doc/TechNotes/vwMemoryMgmt.pdf. Are you using the default memory
settings of VW (so you were using default 7.6 and are now using default
7.7.1) or does your app have any memory settings (e.g. that may need
reworking in the light of the tech note).

Yours faithfully
Niall Ross

>Hi all,
>
> Last month I moved to vwnc 7.7.1, after almost a couple of years in nc 7.6.
>I use GLORP in my applications.
>Before moving, I used to have no problem with memory.
>Now, I often experience memory issues when dealing with GLORP.
>In most of the cases, while I read objects stored in the db,
>VW crashes with a out of memory message.
>
>Did anything memory (or glorp) related change from 7.6 to 7.7.1?
>
>Thank you in advance,
>
> Cheers,
> Alberto
>_______________________________________________
>vwnc mailing list
>[hidden email]
>http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
>
>
>
>

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

Alberto Bacchelli

Re: Memory issues with GLORP and VWNC 7.7.1

Dear Niall,

1) I am using PostgreSQL (before and after moving, the same dbms)

2) From what I know I use the default settings (unless some of my requirements change it)

I will have a look at the vwMemoryMgmt.pdf document, thanks :)

Best Regards,
Alberto

On Dec 16, 2010, at 11:06 AM, Niall Ross wrote:

> Dear Alberto,
> couple of questions that will help memory-savvy VWers (of whom I am not one) to help you.
>
> 1) Which DB are you using?
>
> 2) There were memory changes in VW7.7.1 - look at .../doc/TechNotes/vwMemoryMgmt.pdf. Are you using the default memory settings of VW (so you were using default 7.6 and are now using default 7.7.1) or does your app have any memory settings (e.g. that may need reworking in the light of the tech note).
>
> Yours faithfully
> Niall Ross
>
>> Hi all,
>>
>> Last month I moved to vwnc 7.7.1, after almost a couple of years in nc 7.6.
>> I use GLORP in my applications.
>> Before moving, I used to have no problem with memory.
>> Now, I often experience memory issues when dealing with GLORP.
>> In most of the cases, while I read objects stored in the db,
>> VW crashes with a out of memory message.
>>
>> Did anything memory (or glorp) related change from 7.6 to 7.7.1?
>>
>> Thank you in advance,
>>
>> Cheers,
>> Alberto
>> _______________________________________________
>> vwnc mailing list
>> [hidden email]
>> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
>>
>>
>>
>
>

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

Runar Jordahl

Re: Memory issues with GLORP and VWNC 7.7.1

In reply to this post by Alberto Bacchelli

I have a couple of Glorp / VisualWorks 7.7.1 memory related posted on
my blog http://blog.epigent.com/

Runar Jordahl

2010/12/16 Alberto Bacchelli <[hidden email]>:

> Hi all,
>
> Last month I moved to vwnc 7.7.1, after almost a couple of years in nc 7.6.
> I use GLORP in my applications.
> Before moving, I used to have no problem with memory.
> Now, I often experience memory issues when dealing with GLORP.
> In most of the cases, while I read objects stored in the db,
> VW crashes with a out of memory message.
>
> Did anything memory (or glorp) related change from 7.6 to 7.7.1?
>
> Thank you in advance,
>
> Cheers,
> Alberto
> _______________________________________________
> vwnc mailing list
> [hidden email]
> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
>

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

Alberto Bacchelli

Re: Memory issues with GLORP and VWNC 7.7.1

Thank you so much Runar,
your blog posts are very useful!

Alberto

On Dec 17, 2010, at 9:09 AM, Runar Jordahl wrote:

> I have a couple of Glorp / VisualWorks 7.7.1 memory related posted on
> my blog http://blog.epigent.com/
>
> Runar Jordahl
>
> 2010/12/16 Alberto Bacchelli <[hidden email]>:
>> Hi all,
>>
>> Last month I moved to vwnc 7.7.1, after almost a couple of years in nc 7.6.
>> I use GLORP in my applications.
>> Before moving, I used to have no problem with memory.
>> Now, I often experience memory issues when dealing with GLORP.
>> In most of the cases, while I read objects stored in the db,
>> VW crashes with a out of memory message.
>>
>> Did anything memory (or glorp) related change from 7.6 to 7.7.1?
>>
>> Thank you in advance,
>>
>> Cheers,
>> Alberto
>> _______________________________________________
>> vwnc mailing list
>> [hidden email]
>> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
>>

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

Alan Knight-2

Re: Memory issues with GLORP and VWNC 7.7.1

In reply to this post by Alberto Bacchelli

I can't think of anything that would cause it to not be releasing
memory. I'd say try running the allocation profiler, or simply try
interrupting it when it's doing something where you think it might start
looking like it's running out of memory and see if there are obvious
things taking up lots of memory (huge caches, or other variables
associated with the session). Also, try, in such a circumstance doing a)
session reset b) session logout. Do them separately, and look at memory
consumption after GCing. If the reset gets rid of it, then it probably
means something like the session cache's are growing forever. If the
latter, it might be something associated with the database connection.
If neither, it might be entirely outside of Glorp.

On 2010-12-16 3:13 AM, Alberto Bacchelli wrote:

> Hi all,
>
> Last month I moved to vwnc 7.7.1, after almost a couple of years in nc 7.6.
> I use GLORP in my applications.
> Before moving, I used to have no problem with memory.
> Now, I often experience memory issues when dealing with GLORP.
> In most of the cases, while I read objects stored in the db,
> VW crashes with a out of memory message.
>
> Did anything memory (or glorp) related change from 7.6 to 7.7.1?
>
> Thank you in advance,
>
> Cheers,
> Alberto
> _______________________________________________
> vwnc mailing list
> [hidden email]
> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

--
Alan Knight [|], Engineering Manager, Cincom Smalltalk
[hidden email]
[hidden email]
http://www.cincom.com/smalltalk

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc