Re: Kosmo_int Digest, Vol 55, Issue 3

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Kosmo_int Digest, Vol 55, Issue 3

Fernando Perfumo
Hello Sergio, I would have to send that info first time too, sorry.

Operating system:    Windows 2003 server, 3.99 GB RAM
Kosmo Desktop vers. 2.0 RC1 (20091029)
Java 1.6.0_03, as reported by Kosmo itself,

Memory report ( in megabytes )

Total memory |   Used  | Free
------------------------------
520                |    121   | 398      ,at first window, project opened:
520                |    175   | 345      ,after a zoom to layer (ecw one)
520                |    198   | 321      ,after zoom preview
520                |    202   | 317      ,after panning (about 400 m)
520                |    292   | 228      ,after zooming to layer and
returning to preview

while this test we had:  Active layers: 6 out of  17;
all layers from the Posgresql database except the ecw one, being the active
ones not very populated.
I have to count the number of features, but is not a big number, sure less
than 3000 points with numeric attributes.

The ecw file has 448 MB.

Thanks many,
Fernando.





----- Original Message -----
From: <[hidden email]>
To: <[hidden email]>
Sent: Wednesday, May 23, 2012 12:00 PM
Subject: Kosmo_int Digest, Vol 55, Issue 3


> Send Kosmo_int mailing list submissions to
> [hidden email]
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.saig.es/mailman/listinfo/kosmo_int
> or, via email, send a message with subject or body 'help' to
> [hidden email]
>
> You can reach the person managing the list at
> [hidden email]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Kosmo_int digest..."
>
>
> Today's Topics:
>
>   1. Fw: about memory use (Fernando Perfumo)
>   2. Re: Fw: about memory use (Sergio Ba?os Calvo)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 23 May 2012 09:46:23 +0200
> From: "Fernando Perfumo" <[hidden email]>
> Subject: [Kosmo_int] Fw: about memory use
> To: <[hidden email]>
> Message-ID: <D92F0E0C34BF4A818E88BF009F4B3756@PCPERFUMO>
> Content-Type: text/plain; format=flowed; charset="iso-8859-1";
> reply-type=response
>
>
>
>
> Hello,
>
> I'm using Kosmo desktop 2.0 and PostgreSQL.
> The base image is a .ecw file of about 500 MB.
>
> I noticed that panning the map exhaust the system memory, and I need to
> free
> it frecuently by hand.
>
> Does somebody know  the reason to keep the memory recovery an user option?
>
> Wouldn't be better freeing the user of this task?
>
> I use Kosmo for a traffic ligths control gis, and found it a very good
> application, despite java gas-like behaviour.
>
> Thanks
>
> Fernando Perfumo Velazquez
>
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 23 May 2012 10:08:25 +0200
> From: Sergio Ba?os Calvo <[hidden email]>
> Subject: Re: [Kosmo_int] Fw: about memory use
> To: "International Kosmo mailing list (english languaje)"
> <[hidden email]>
> Message-ID: <[hidden email]>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Good morning Fernando.
>
> The scenario you're talking about (PostgreSQL layers + base ecw image
> layer) is very usual with Kosmo Desktop and we haven't found issues
> about memory exhausting while panning before: we have systems that are
> using 500 Gb image directories as base image layer plus 10.000.000+
> feature PostgreSQL layers and it doesn't have that behaviour.
>
> Could you give me some more info about your current scenario in order to
> give you some hints?
>
> - Kosmo Desktop version: 2.0, 2.0 rc1 or 2.0.1?
>
> - PostgreSQL layers:
>
> + Number of features
> + Geometry types
> + Number of layers
>
> - Base image layer
>
> + Is it an unique file or a mosaic of them?
>
> - Are there more layers loaded (shapefiles, CAD files, etc.) apart from
> them?
>
>
> The memory recovery button is just inherited from the base JUMP, but it
> shouldn't be necessary to use it at all: when Java VM hits the maximum
> available memory it should make automatically the same call to the
> garbage collector as the button does.
>
>
> Tip: in your Kosmo.bat/Kosmo.sh launcher, you can set up more memory for
> your Kosmo Desktop installation in order to increase performance if you
> have enough memory in your system.
>
> SET PATH=..\dlls;%PATH%
> start.\jre\bin\javaw -Djava.library.path="..\dlls" -cp .;./saig.jar
> -Xmx800M com.vividsolutions.jump.workbench.JUMPWorkbench
> -plug-in-directory ./ext
>
> Change -Xmx800M to -Xmx1024M or -Xmx1200M to see if the application
> behaves better.
>
> Regards,
>
> El 23/05/2012 9:46, Fernando Perfumo escribió:
>>
>>
>>
>> Hello,
>>
>> I'm using Kosmo desktop 2.0 and PostgreSQL.
>> The base image is a .ecw file of about 500 MB.
>>
>> I noticed that panning the map exhaust the system memory, and I need
>> to free
>> it frecuently by hand.
>>
>> Does somebody know  the reason to keep the memory recovery an user
>> option?
>>
>> Wouldn't be better freeing the user of this task?
>>
>> I use Kosmo for a traffic ligths control gis, and found it a very good
>> application, despite java gas-like behaviour.
>>
>> Thanks
>>
>> Fernando Perfumo Velazquez
>>
>> _______________________________________________
>> Kosmo_int mailing list
>> [hidden email]
>> http://lists.saig.es/mailman/listinfo/kosmo_int
>>
>
>
> --
>
> Sergio Baños Calvo
>
> Jefe de desarrollos
> Sistemas Abiertos de Información Geográfica, S.L. (SAIG S.L.)
> Tlfno. móvil: 685005960
> Tlfno. fijo: (+34) 954788876
>
> E-mail: [hidden email]
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://lists.saig.es/pipermail/kosmo_int/attachments/20120523/9e2e6641/attachment-0001.html
>
> ------------------------------
>
> _______________________________________________
> Kosmo_int mailing list
> [hidden email]
> http://lists.saig.es/mailman/listinfo/kosmo_int
>
>
> End of Kosmo_int Digest, Vol 55, Issue 3
> ****************************************

_______________________________________________
Kosmo_int mailing list
[hidden email]
http://lists.saig.es/mailman/listinfo/kosmo_int
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Kosmo_int Digest, Vol 55, Issue 3

Rahkonen Jukka
Hi,

I had a little test with PostGIS and ECW layers (4 GB ECW file) by panning and zooming and checking the memory consumption reported by Kosmo system info. Numbers go up and down, sometimes only 7 MB of free memory was reported but after next zoom the amount of free memory was 150 MB.  Everything worked fluently for me all of the time. Pressing the Garbage Collect button usually increased the amount of free memory that was reported it did not make Kosmo any faster to use. It looks that in my environment (Windows XP, Java 1.6.0_26) and test data the memory handling is working well.

Do you have some real problems so that you get out of memory errors while using Kosmo? Or does Kosmo get slow but after doing Garbage Collect it is fast again? Or are you just thinking that the system does not work correctly because after pressing Garbage Collect the amount of free menory on the report is higher?

-Jukka Rahkonen-

Fernando Perfumo wrote:

>
> Hello Sergio, I would have to send that info first time too, sorry.
>
> Operating system:    Windows 2003 server, 3.99 GB RAM
> Kosmo Desktop vers. 2.0 RC1 (20091029)
> Java 1.6.0_03, as reported by Kosmo itself,
>
> Memory report ( in megabytes )
>
> Total memory |   Used  | Free
> ------------------------------
> 520                |    121   | 398      ,at first window,
> project opened:
> 520                |    175   | 345      ,after a zoom to
> layer (ecw one)
> 520                |    198   | 321      ,after zoom preview
> 520                |    202   | 317      ,after panning (about 400 m)
> 520                |    292   | 228      ,after zooming to layer and
> returning to preview
>
> while this test we had:  Active layers: 6 out of  17;
> all layers from the Posgresql database except the ecw one,
> being the active
> ones not very populated.
> I have to count the number of features, but is not a big
> number, sure less
> than 3000 points with numeric attributes.
>
> The ecw file has 448 MB.
>
> Thanks many,
> Fernando.
>
>
>
>
>
> ----- Original Message -----
> From: <[hidden email]>
> To: <[hidden email]>
> Sent: Wednesday, May 23, 2012 12:00 PM
> Subject: Kosmo_int Digest, Vol 55, Issue 3
>
>
> > Send Kosmo_int mailing list submissions to
> > [hidden email]
> >
> > To subscribe or unsubscribe via the World Wide Web, visit
> > http://lists.saig.es/mailman/listinfo/kosmo_int
> > or, via email, send a message with subject or body 'help' to
> > [hidden email]
> >
> > You can reach the person managing the list at
> > [hidden email]
> >
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of Kosmo_int digest..."
> >
> >
> > Today's Topics:
> >
> >   1. Fw: about memory use (Fernando Perfumo)
> >   2. Re: Fw: about memory use (Sergio Ba?os Calvo)
> >
> >
> >
> ----------------------------------------------------------------------
> >
> > Message: 1
> > Date: Wed, 23 May 2012 09:46:23 +0200
> > From: "Fernando Perfumo" <[hidden email]>
> > Subject: [Kosmo_int] Fw: about memory use
> > To: <[hidden email]>
> > Message-ID: <D92F0E0C34BF4A818E88BF009F4B3756@PCPERFUMO>
> > Content-Type: text/plain; format=flowed; charset="iso-8859-1";
> > reply-type=response
> >
> >
> >
> >
> > Hello,
> >
> > I'm using Kosmo desktop 2.0 and PostgreSQL.
> > The base image is a .ecw file of about 500 MB.
> >
> > I noticed that panning the map exhaust the system memory,
> and I need to
> > free
> > it frecuently by hand.
> >
> > Does somebody know  the reason to keep the memory recovery
> an user option?
> >
> > Wouldn't be better freeing the user of this task?
> >
> > I use Kosmo for a traffic ligths control gis, and found it
> a very good
> > application, despite java gas-like behaviour.
> >
> > Thanks
> >
> > Fernando Perfumo Velazquez
> >
> >
> >
> > ------------------------------
> >
> > Message: 2
> > Date: Wed, 23 May 2012 10:08:25 +0200
> > From: Sergio Ba?os Calvo <[hidden email]>
> > Subject: Re: [Kosmo_int] Fw: about memory use
> > To: "International Kosmo mailing list (english languaje)"
> > <[hidden email]>
> > Message-ID: <[hidden email]>
> > Content-Type: text/plain; charset="iso-8859-1"
> >
> > Good morning Fernando.
> >
> > The scenario you're talking about (PostgreSQL layers + base
> ecw image
> > layer) is very usual with Kosmo Desktop and we haven't found issues
> > about memory exhausting while panning before: we have
> systems that are
> > using 500 Gb image directories as base image layer plus 10.000.000+
> > feature PostgreSQL layers and it doesn't have that behaviour.
> >
> > Could you give me some more info about your current
> scenario in order to
> > give you some hints?
> >
> > - Kosmo Desktop version: 2.0, 2.0 rc1 or 2.0.1?
> >
> > - PostgreSQL layers:
> >
> > + Number of features
> > + Geometry types
> > + Number of layers
> >
> > - Base image layer
> >
> > + Is it an unique file or a mosaic of them?
> >
> > - Are there more layers loaded (shapefiles, CAD files,
> etc.) apart from
> > them?
> >
> >
> > The memory recovery button is just inherited from the base
> JUMP, but it
> > shouldn't be necessary to use it at all: when Java VM hits
> the maximum
> > available memory it should make automatically the same call to the
> > garbage collector as the button does.
> >
> >
> > Tip: in your Kosmo.bat/Kosmo.sh launcher, you can set up
> more memory for
> > your Kosmo Desktop installation in order to increase
> performance if you
> > have enough memory in your system.
> >
> > SET PATH=..\dlls;%PATH%
> > start.\jre\bin\javaw -Djava.library.path="..\dlls" -cp .;./saig.jar
> > -Xmx800M com.vividsolutions.jump.workbench.JUMPWorkbench
> > -plug-in-directory ./ext
> >
> > Change -Xmx800M to -Xmx1024M or -Xmx1200M to see if the application
> > behaves better.
> >
> > Regards,
> >
> > El 23/05/2012 9:46, Fernando Perfumo escribió:
> >>
> >>
> >>
> >> Hello,
> >>
> >> I'm using Kosmo desktop 2.0 and PostgreSQL.
> >> The base image is a .ecw file of about 500 MB.
> >>
> >> I noticed that panning the map exhaust the system memory,
> and I need
> >> to free
> >> it frecuently by hand.
> >>
> >> Does somebody know  the reason to keep the memory recovery an user
> >> option?
> >>
> >> Wouldn't be better freeing the user of this task?
> >>
> >> I use Kosmo for a traffic ligths control gis, and found it
> a very good
> >> application, despite java gas-like behaviour.
> >>
> >> Thanks
> >>
> >> Fernando Perfumo Velazquez
> >>
> >> _______________________________________________
> >> Kosmo_int mailing list
> >> [hidden email]
> >> http://lists.saig.es/mailman/listinfo/kosmo_int
> >>
> >
> >
> > --
> >
> > Sergio Baños Calvo
> >
> > Jefe de desarrollos
> > Sistemas Abiertos de Información Geográfica, S.L. (SAIG S.L.)
> > Tlfno. móvil: 685005960
> > Tlfno. fijo: (+34) 954788876
> >
> > E-mail: [hidden email]
> >
> > -------------- next part --------------
> > An HTML attachment was scrubbed...
> > URL:
> >
> http://lists.saig.es/pipermail/kosmo_int/attachments/20120523/
> 9e2e6641/attachment-0001.html
> >
> > ------------------------------
> >
> > _______________________________________________
> > Kosmo_int mailing list
> > [hidden email]
> > http://lists.saig.es/mailman/listinfo/kosmo_int
> >
> >
> > End of Kosmo_int Digest, Vol 55, Issue 3
> > ****************************************
>
> _______________________________________________
> Kosmo_int mailing list
> [hidden email]
> http://lists.saig.es/mailman/listinfo/kosmo_int
> _______________________________________________
Kosmo_int mailing list
[hidden email]
http://lists.saig.es/mailman/listinfo/kosmo_int
Loading...