[Geoserver-devel] questions about JaiMemoryCapacity

Hi all,

I ran into an issue when recently running wms cite tests. It seems that in some configurations JaiMemoryCapacity is a double, and a percentage of available memory, example "0.5". But in other configurations it seems it is a long, and an absolute value, example "209715200".

My question is which one wins? If you look at GeoServerDTO.Defaults.JaiMemoryCapacity it would point to long but GeoServerDTO.getJaiMemoryCapacity() it points to double.

After talking to Andrea on IRC it seems the double is the way to go. But I am confused why i have not run into this issue before... since I have run wms cite tests many times with the new configuration stuff on 1.7.

Anyone have an idea of what may be causing this?

-Justin

--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.

Hi Justin,

in general the Jai Memory Capacity is a long representing the amount
of memory to be set ... in the geoserver specific case, at a certain
point the configuration value was changed ad a percentage of the total
amount of the available run-time memory.

Simone did this change, as soon as he will connect again will provide
more details on this.

Cheers,
        Alessio.

-------------------------------------------------------
Eng. Alessio Fabiani
Vice-President /CTO GeoSolutions S.A.S.
Via Carignoni 51
55041 Camaiore (LU)
Italy

phone: +39 0584983027
fax: +39 0584983027
mob: +39 349 8227000

http://www.geo-solutions.it

-------------------------------------------------------

On Fri, Dec 5, 2008 at 4:48 PM, Justin Deoliveira <jdeolive@anonymised.com> wrote:

Hi all,

I ran into an issue when recently running wms cite tests. It seems that
in some configurations JaiMemoryCapacity is a double, and a percentage
of available memory, example "0.5". But in other configurations it seems
it is a long, and an absolute value, example "209715200".

My question is which one wins? If you look at
GeoServerDTO.Defaults.JaiMemoryCapacity it would point to long but
GeoServerDTO.getJaiMemoryCapacity() it points to double.

After talking to Andrea on IRC it seems the double is the way to go. But
I am confused why i have not run into this issue before... since I have
run wms cite tests many times with the new configuration stuff on 1.7.

Anyone have an idea of what may be causing this?

-Justin

--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.

------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

ehm , actually andrea did it :slight_smile:

Simone.
-------------------------------------------------------
Ing. Simone Giannecchini
GeoSolutions S.A.S.
Owner - Software Engineer
Via Carignoni 51
55041 Camaiore (LU)
Italy

phone: +39 0584983027
fax: +39 0584983027
mob: +39 333 8128928

http://www.geo-solutions.it
http://simboss.blogspot.com/
http://www.linkedin.com/in/simonegiannecchini

-------------------------------------------------------

On Fri, Dec 5, 2008 at 5:25 PM, Alessio Fabiani
<alessio.fabiani@anonymised.com> wrote:

Hi Justin,

in general the Jai Memory Capacity is a long representing the amount
of memory to be set ... in the geoserver specific case, at a certain
point the configuration value was changed ad a percentage of the total
amount of the available run-time memory.

Simone did this change, as soon as he will connect again will provide
more details on this.

Cheers,
       Alessio.

-------------------------------------------------------
Eng. Alessio Fabiani
Vice-President /CTO GeoSolutions S.A.S.
Via Carignoni 51
55041 Camaiore (LU)
Italy

phone: +39 0584983027
fax: +39 0584983027
mob: +39 349 8227000

http://www.geo-solutions.it

-------------------------------------------------------

On Fri, Dec 5, 2008 at 4:48 PM, Justin Deoliveira <jdeolive@anonymised.com> wrote:

Hi all,

I ran into an issue when recently running wms cite tests. It seems that
in some configurations JaiMemoryCapacity is a double, and a percentage
of available memory, example "0.5". But in other configurations it seems
it is a long, and an absolute value, example "209715200".

My question is which one wins? If you look at
GeoServerDTO.Defaults.JaiMemoryCapacity it would point to long but
GeoServerDTO.getJaiMemoryCapacity() it points to double.

After talking to Andrea on IRC it seems the double is the way to go. But
I am confused why i have not run into this issue before... since I have
run wms cite tests many times with the new configuration stuff on 1.7.

Anyone have an idea of what may be causing this?

-Justin

--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.

------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Ok.. so it sounds like the double / percentage value is the way to go. I have proceeded accordingly.

Simone Giannecchini wrote:

ehm , actually andrea did it :slight_smile:

Simone.
-------------------------------------------------------
Ing. Simone Giannecchini
GeoSolutions S.A.S.
Owner - Software Engineer
Via Carignoni 51
55041 Camaiore (LU)
Italy

phone: +39 0584983027
fax: +39 0584983027
mob: +39 333 8128928

http://www.geo-solutions.it
http://simboss.blogspot.com/
http://www.linkedin.com/in/simonegiannecchini

-------------------------------------------------------

On Fri, Dec 5, 2008 at 5:25 PM, Alessio Fabiani
<alessio.fabiani@anonymised.com> wrote:

Hi Justin,

in general the Jai Memory Capacity is a long representing the amount
of memory to be set ... in the geoserver specific case, at a certain
point the configuration value was changed ad a percentage of the total
amount of the available run-time memory.

Simone did this change, as soon as he will connect again will provide
more details on this.

Cheers,
       Alessio.

-------------------------------------------------------
Eng. Alessio Fabiani
Vice-President /CTO GeoSolutions S.A.S.
Via Carignoni 51
55041 Camaiore (LU)
Italy

phone: +39 0584983027
fax: +39 0584983027
mob: +39 349 8227000

http://www.geo-solutions.it

-------------------------------------------------------

On Fri, Dec 5, 2008 at 4:48 PM, Justin Deoliveira <jdeolive@anonymised.com> wrote:

Hi all,

I ran into an issue when recently running wms cite tests. It seems that
in some configurations JaiMemoryCapacity is a double, and a percentage
of available memory, example "0.5". But in other configurations it seems
it is a long, and an absolute value, example "209715200".

My question is which one wins? If you look at
GeoServerDTO.Defaults.JaiMemoryCapacity it would point to long but
GeoServerDTO.getJaiMemoryCapacity() it points to double.

After talking to Andrea on IRC it seems the double is the way to go. But
I am confused why i have not run into this issue before... since I have
run wms cite tests many times with the new configuration stuff on 1.7.

Anyone have an idea of what may be causing this?

-Justin

--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.

------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.

Yep,
I think that it is much better than using an absolute value, since if
the value of the tileache capacity goes beyond or even to close to the
available runtime memory we could easily get into troubles.

Simone.
-------------------------------------------------------
Ing. Simone Giannecchini
GeoSolutions S.A.S.
Owner - Software Engineer
Via Carignoni 51
55041 Camaiore (LU)
Italy

phone: +39 0584983027
fax: +39 0584983027
mob: +39 333 8128928

http://www.geo-solutions.it
http://simboss.blogspot.com/
http://www.linkedin.com/in/simonegiannecchini

-------------------------------------------------------

On Sat, Dec 6, 2008 at 5:30 PM, Justin Deoliveira <jdeolive@anonymised.com> wrote:

Ok.. so it sounds like the double / percentage value is the way to go. I
have proceeded accordingly.

Simone Giannecchini wrote:

ehm , actually andrea did it :slight_smile:

Simone.
-------------------------------------------------------
Ing. Simone Giannecchini
GeoSolutions S.A.S.
Owner - Software Engineer
Via Carignoni 51
55041 Camaiore (LU)
Italy

phone: +39 0584983027
fax: +39 0584983027
mob: +39 333 8128928

http://www.geo-solutions.it
http://simboss.blogspot.com/
http://www.linkedin.com/in/simonegiannecchini

-------------------------------------------------------

On Fri, Dec 5, 2008 at 5:25 PM, Alessio Fabiani
<alessio.fabiani@anonymised.com> wrote:

Hi Justin,

in general the Jai Memory Capacity is a long representing the amount
of memory to be set ... in the geoserver specific case, at a certain
point the configuration value was changed ad a percentage of the total
amount of the available run-time memory.

Simone did this change, as soon as he will connect again will provide
more details on this.

Cheers,
      Alessio.

-------------------------------------------------------
Eng. Alessio Fabiani
Vice-President /CTO GeoSolutions S.A.S.
Via Carignoni 51
55041 Camaiore (LU)
Italy

phone: +39 0584983027
fax: +39 0584983027
mob: +39 349 8227000

http://www.geo-solutions.it

-------------------------------------------------------

On Fri, Dec 5, 2008 at 4:48 PM, Justin Deoliveira <jdeolive@anonymised.com>
wrote:

Hi all,

I ran into an issue when recently running wms cite tests. It seems that
in some configurations JaiMemoryCapacity is a double, and a percentage
of available memory, example "0.5". But in other configurations it seems
it is a long, and an absolute value, example "209715200".

My question is which one wins? If you look at
GeoServerDTO.Defaults.JaiMemoryCapacity it would point to long but
GeoServerDTO.getJaiMemoryCapacity() it points to double.

After talking to Andrea on IRC it seems the double is the way to go. But
I am confused why i have not run into this issue before... since I have
run wms cite tests many times with the new configuration stuff on 1.7.

Anyone have an idea of what may be causing this?

-Justin

--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.

------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas,
Nevada.
The future of the web can't happen without you. Join us at MIX09 to
help
pave the way to the Next Web now. Learn more and register at

http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas,
Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at

http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas,
Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at

http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.