Tooltip performance
|
|
KeithC
|
Some javascript/style in this post has been disabled (why?)
I'm finding that the performance of the tooltips is varying greatly and I'd like to understand what is going on behind the scenes and therefore what factors are affecting this. Presumably when the cursor s moved over the map, a mouseover event is triggered and this sends the position information and state of the layers is sent back to the server via an xmlhttprequest. The web extensions are used to identify what object on what layer is at the map location, and the tooltip data is queried and returned to the client, which is then displayed. So factors affecting this process will be what is happening on the client machine, the network, and the server at the time the process occurs. The performance seems to change a great deal from very good to unacceptably slow (the user would give up). I find this change strange because other applications (e.g. MapGuide 6.x) run from the same client to the same server are not varying nearly as much. It is also strange in that the initial request for the layout and subsequent requests for layer data are not particularly slow when the tooltips are. Are there any settings which can be altered to improve this? This kind of unreliability could almost rule this technology out in my view. Keith This email and any attached files are confidential and copyright protected. If you are not the addressee, any dissemination of this communication is strictly prohibited. Unless otherwise expressly agreed in writing, nothing stated in this communication shall be legally binding. |
||||||||||||||||
Trevor Wekel
|
Some javascript/style in this post has been disabled (why?)
Hi Keith,
You are correct with the basic flow of events for
generating the tooltips. The AJAX client sends the map coordinates of the
point along with the map name to the Web Extensions. The Web
Extensions in turn, forwards this information to the Server.
Once at the server, all of the layers in the map are queried to see
if they have any features underneath the point. Since every layer is
queried, the performance will depend on the number of layers in
the Map. Each FeatureSource for each layer will be queried. If
you have a number of layers from external databases, the database will be
queried for each layer.
Feature Service connection pooling and caching may
help. These are controlled by the following settings in serverconfig.ini
and should be accessible from Server Admin.
[FeatureServiceProperties]
DataConnectionPoolSize =
20
DataConnectionPoolExcludedProviders = OSGeo.SDF,OSGeo.SHP DataConnectionPoolEnabled = 1 DataCacheSize = 100 CacheSize = 100 Just as a side note, I think MapGuide 6.x handles tooltip
generation client side. I don't think it goes back to the server so it
will be less affected by server load.
Thanks,
Trevor From: Campbell, Keith A [mailto:keith.campbell@...] Sent: Friday, November 17, 2006 6:53 AM To: users@... Subject: Tooltip performance I'm finding that the performance of the tooltips is varying greatly and I'd like to understand what is going on behind the scenes and therefore what factors are affecting this. Presumably when the cursor s moved over the map, a mouseover event is triggered and this sends the position information and state of the layers is sent back to the server via an xmlhttprequest. The web extensions are used to identify what object on what layer is at the map location, and the tooltip data is queried and returned to the client, which is then displayed. So factors affecting this process will be what is happening on the client machine, the network, and the server at the time the process occurs. The performance seems to change a great deal from very good to unacceptably slow (the user would give up). I find this change strange because other applications (e.g. MapGuide 6.x) run from the same client to the same server are not varying nearly as much. It is also strange in that the initial request for the layout and subsequent requests for layer data are not particularly slow when the tooltips are. Are there any settings which can be altered to improve this? This kind of unreliability could almost rule this technology out in my view. Keith This email and any attached files are confidential and copyright protected. If you are not the addressee, any dissemination of this communication is strictly prohibited. Unless otherwise expressly agreed in writing, nothing stated in this communication shall be legally binding. |
|
Trevor Wekel
|
In reply to this post by KeithC
Some javascript/style in this post has been disabled (why?)
Hi Keith,
You can also disable selection for layers which do
not require tooltips. If a layer is not selectable, it is not included in
the query.
Thanks,
Trevor From: Trevor Wekel Sent: Friday, November 17, 2006 10:54 AM To: 'Campbell, Keith A'; users@... Subject: RE: Tooltip performance Hi Keith,
You are correct with the basic flow of events for
generating the tooltips. The AJAX client sends the map coordinates of the
point along with the map name to the Web Extensions. The Web
Extensions in turn, forwards this information to the Server.
Once at the server, all of the layers in the map are queried to see
if they have any features underneath the point. Since every layer is
queried, the performance will depend on the number of layers in
the Map. Each FeatureSource for each layer will be queried. If
you have a number of layers from external databases, the database will be
queried for each layer.
Feature Service connection pooling and caching may
help. These are controlled by the following settings in serverconfig.ini
and should be accessible from Server Admin.
[FeatureServiceProperties]
DataConnectionPoolSize =
20
DataConnectionPoolExcludedProviders = OSGeo.SDF,OSGeo.SHP DataConnectionPoolEnabled = 1 DataCacheSize = 100 CacheSize = 100 Just as a side note, I think MapGuide 6.x handles tooltip
generation client side. I don't think it goes back to the server so it
will be less affected by server load.
Thanks,
Trevor From: Campbell, Keith A [mailto:keith.campbell@...] Sent: Friday, November 17, 2006 6:53 AM To: users@... Subject: Tooltip performance I'm finding that the performance of the tooltips is varying greatly and I'd like to understand what is going on behind the scenes and therefore what factors are affecting this. Presumably when the cursor s moved over the map, a mouseover event is triggered and this sends the position information and state of the layers is sent back to the server via an xmlhttprequest. The web extensions are used to identify what object on what layer is at the map location, and the tooltip data is queried and returned to the client, which is then displayed. So factors affecting this process will be what is happening on the client machine, the network, and the server at the time the process occurs. The performance seems to change a great deal from very good to unacceptably slow (the user would give up). I find this change strange because other applications (e.g. MapGuide 6.x) run from the same client to the same server are not varying nearly as much. It is also strange in that the initial request for the layout and subsequent requests for layer data are not particularly slow when the tooltips are. Are there any settings which can be altered to improve this? This kind of unreliability could almost rule this technology out in my view. Keith This email and any attached files are confidential and copyright protected. If you are not the addressee, any dissemination of this communication is strictly prohibited. Unless otherwise expressly agreed in writing, nothing stated in this communication shall be legally binding. |
||||||||||||||||
Jason Birch
|
In reply to this post by KeithC
Some javascript/style in this post has been disabled (why?)
Is it just
layers that have had their selectability
property cleared that will be ignored, or will not setting a maptip have the
same effect?
Jason From: Trevor Wekel [mailto:trevor.wekel@...] Sent: Friday, November 17, 2006 10:15 To: Campbell, Keith A; users@... Subject: [mapguide-users] RE: Tooltip performance Hi Keith,
You can also disable selection for layers which do
not require tooltips. If a layer is not selectable, it is not included in
the query.
Thanks,
Trevor From: Trevor Wekel Sent: Friday, November 17, 2006 10:54 AM To: 'Campbell, Keith A'; users@... Subject: RE: Tooltip performance Hi Keith,
You are correct with the basic flow of events for
generating the tooltips. The AJAX client sends the map coordinates of the
point along with the map name to the Web Extensions. The Web
Extensions in turn, forwards this information to the Server.
Once at the server, all of the layers in the map are queried to see
if they have any features underneath the point. Since every layer is
queried, the performance will depend on the number of layers in
the Map. Each FeatureSource for each layer will be queried. If
you have a number of layers from external databases, the database will be
queried for each layer.
Feature Service connection pooling and caching may
help. These are controlled by the following settings in serverconfig.ini
and should be accessible from Server Admin.
[FeatureServiceProperties]
DataConnectionPoolSize =
20
DataConnectionPoolExcludedProviders = OSGeo.SDF,OSGeo.SHP DataConnectionPoolEnabled = 1 DataCacheSize = 100 CacheSize = 100 Just as a side note, I think MapGuide 6.x handles tooltip
generation client side. I don't think it goes back to the server so it
will be less affected by server load.
Thanks,
Trevor From: Campbell, Keith A [mailto:keith.campbell@...] Sent: Friday, November 17, 2006 6:53 AM To: users@... Subject: Tooltip performance I'm finding that the performance of the tooltips is varying greatly and I'd like to understand what is going on behind the scenes and therefore what factors are affecting this. Presumably when the cursor s moved over the map, a mouseover event is triggered and this sends the position information and state of the layers is sent back to the server via an xmlhttprequest. The web extensions are used to identify what object on what layer is at the map location, and the tooltip data is queried and returned to the client, which is then displayed. So factors affecting this process will be what is happening on the client machine, the network, and the server at the time the process occurs. The performance seems to change a great deal from very good to unacceptably slow (the user would give up). I find this change strange because other applications (e.g. MapGuide 6.x) run from the same client to the same server are not varying nearly as much. It is also strange in that the initial request for the layout and subsequent requests for layer data are not particularly slow when the tooltips are. Are there any settings which can be altered to improve this? This kind of unreliability could almost rule this technology out in my view. Keith This email and any attached files are confidential and copyright protected. If you are not the addressee, any dissemination of this communication is strictly prohibited. Unless otherwise expressly agreed in writing, nothing stated in this communication shall be legally binding. |
||||||||||||||||
Andy Morsell
|
In reply to this post by Trevor Wekel
Some javascript/style in this post has been disabled (why?)
Why is each FeatureSource for each layer queried when it is
only the top-most layer in the display priority that should display the
tooltip?
Andy From: Trevor Wekel [mailto:trevor.wekel@...] Sent: Friday, November 17, 2006 9:54 AM To: Campbell, Keith A; users@... Subject: [mapguide-users] RE: Tooltip performance Hi Keith,
You are correct with the basic flow of events for
generating the tooltips. The AJAX client sends the map coordinates of the
point along with the map name to the Web Extensions. The Web
Extensions in turn, forwards this information to the Server.
Once at the server, all of the layers in the map are queried to see
if they have any features underneath the point. Since every layer is
queried, the performance will depend on the number of layers in
the Map. Each FeatureSource for each layer will be queried. If
you have a number of layers from external databases, the database will be
queried for each layer.
Feature Service connection pooling and caching may
help. These are controlled by the following settings in serverconfig.ini
and should be accessible from Server Admin.
[FeatureServiceProperties]
DataConnectionPoolSize =
20
DataConnectionPoolExcludedProviders = OSGeo.SDF,OSGeo.SHP DataConnectionPoolEnabled = 1 DataCacheSize = 100 CacheSize = 100 Just as a side note, I think MapGuide 6.x handles tooltip
generation client side. I don't think it goes back to the server so it
will be less affected by server load.
Thanks,
Trevor From: Campbell, Keith A [mailto:keith.campbell@...] Sent: Friday, November 17, 2006 6:53 AM To: users@... Subject: Tooltip performance I'm finding that the performance of the tooltips is varying greatly and I'd like to understand what is going on behind the scenes and therefore what factors are affecting this. Presumably when the cursor s moved over the map, a mouseover event is triggered and this sends the position information and state of the layers is sent back to the server via an xmlhttprequest. The web extensions are used to identify what object on what layer is at the map location, and the tooltip data is queried and returned to the client, which is then displayed. So factors affecting this process will be what is happening on the client machine, the network, and the server at the time the process occurs. The performance seems to change a great deal from very good to unacceptably slow (the user would give up). I find this change strange because other applications (e.g. MapGuide 6.x) run from the same client to the same server are not varying nearly as much. It is also strange in that the initial request for the layout and subsequent requests for layer data are not particularly slow when the tooltips are. Are there any settings which can be altered to improve this? This kind of unreliability could almost rule this technology out in my view. Keith This email and any attached files are confidential and copyright protected. If you are not the addressee, any dissemination of this communication is strictly prohibited. Unless otherwise expressly agreed in writing, nothing stated in this communication shall be legally binding. |
||||||||||||||||
|
Jason Birch
|
In reply to this post by KeithC
Some javascript/style in this post has been disabled (why?)
Yes, ideally layers with tooltip properties set would
be queried top-down until there is a hit, and then the loop would short
circuit.
Jason From: Andy Morsell [mailto:amorsell@...] Sent: Friday, November 17, 2006 10:19 To: users@... Subject: RE: [mapguide-users] RE: Tooltip performance Why is each FeatureSource for each layer queried when it is
only the top-most layer in the display priority that should display the
tooltip?
Andy From: Trevor Wekel [mailto:trevor.wekel@...] Sent: Friday, November 17, 2006 9:54 AM To: Campbell, Keith A; users@... Subject: [mapguide-users] RE: Tooltip performance Hi Keith,
You are correct with the basic flow of events for
generating the tooltips. The AJAX client sends the map coordinates of the
point along with the map name to the Web Extensions. The Web
Extensions in turn, forwards this information to the Server.
Once at the server, all of the layers in the map are queried to see
if they have any features underneath the point. Since every layer is
queried, the performance will depend on the number of layers in
the Map. Each FeatureSource for each layer will be queried. If
you have a number of layers from external databases, the database will be
queried for each layer.
Feature Service connection pooling and caching may
help. These are controlled by the following settings in serverconfig.ini
and should be accessible from Server Admin.
[FeatureServiceProperties]
DataConnectionPoolSize =
20
DataConnectionPoolExcludedProviders = OSGeo.SDF,OSGeo.SHP DataConnectionPoolEnabled = 1 DataCacheSize = 100 CacheSize = 100 Just as a side note, I think MapGuide 6.x handles tooltip
generation client side. I don't think it goes back to the server so it
will be less affected by server load.
Thanks,
Trevor From: Campbell, Keith A [mailto:keith.campbell@...] Sent: Friday, November 17, 2006 6:53 AM To: users@... Subject: Tooltip performance I'm finding that the performance of the tooltips is varying greatly and I'd like to understand what is going on behind the scenes and therefore what factors are affecting this. Presumably when the cursor s moved over the map, a mouseover event is triggered and this sends the position information and state of the layers is sent back to the server via an xmlhttprequest. The web extensions are used to identify what object on what layer is at the map location, and the tooltip data is queried and returned to the client, which is then displayed. So factors affecting this process will be what is happening on the client machine, the network, and the server at the time the process occurs. The performance seems to change a great deal from very good to unacceptably slow (the user would give up). I find this change strange because other applications (e.g. MapGuide 6.x) run from the same client to the same server are not varying nearly as much. It is also strange in that the initial request for the layout and subsequent requests for layer data are not particularly slow when the tooltips are. Are there any settings which can be altered to improve this? This kind of unreliability could almost rule this technology out in my view. Keith This email and any attached files are confidential and copyright protected. If you are not the addressee, any dissemination of this communication is strictly prohibited. Unless otherwise expressly agreed in writing, nothing stated in this communication shall be legally binding. |
||||||||||||||||
|
Andy Morsell
|
Some javascript/style in this post has been disabled (why?)
Or, the one single layer to fetch tooltip information for
could be pre-determined by the variables of display priority, selectability, and
whether they have a tooltip definition. Then, only one query would
occur.
Andy From: Jason Birch [mailto:Jason.Birch@...] Sent: Friday, November 17, 2006 10:22 AM To: users@... Subject: RE: [mapguide-users] RE: Tooltip performance Yes, ideally layers with tooltip properties set would
be queried top-down until there is a hit, and then the loop would short
circuit.
Jason From: Andy Morsell [mailto:amorsell@...] Sent: Friday, November 17, 2006 10:19 To: users@... Subject: RE: [mapguide-users] RE: Tooltip performance Why is each FeatureSource for each layer queried when it is
only the top-most layer in the display priority that should display the
tooltip?
Andy From: Trevor Wekel [mailto:trevor.wekel@...] Sent: Friday, November 17, 2006 9:54 AM To: Campbell, Keith A; users@... Subject: [mapguide-users] RE: Tooltip performance Hi Keith,
You are correct with the basic flow of events for
generating the tooltips. The AJAX client sends the map coordinates of the
point along with the map name to the Web Extensions. The Web
Extensions in turn, forwards this information to the Server.
Once at the server, all of the layers in the map are queried to see
if they have any features underneath the point. Since every layer is
queried, the performance will depend on the number of layers in
the Map. Each FeatureSource for each layer will be queried. If
you have a number of layers from external databases, the database will be
queried for each layer.
Feature Service connection pooling and caching may
help. These are controlled by the following settings in serverconfig.ini
and should be accessible from Server Admin.
[FeatureServiceProperties]
DataConnectionPoolSize =
20
DataConnectionPoolExcludedProviders = OSGeo.SDF,OSGeo.SHP DataConnectionPoolEnabled = 1 DataCacheSize = 100 CacheSize = 100 Just as a side note, I think MapGuide 6.x handles tooltip
generation client side. I don't think it goes back to the server so it
will be less affected by server load.
Thanks,
Trevor From: Campbell, Keith A [mailto:keith.campbell@...] Sent: Friday, November 17, 2006 6:53 AM To: users@... Subject: Tooltip performance I'm finding that the performance of the tooltips is varying greatly and I'd like to understand what is going on behind the scenes and therefore what factors are affecting this. Presumably when the cursor s moved over the map, a mouseover event is triggered and this sends the position information and state of the layers is sent back to the server via an xmlhttprequest. The web extensions are used to identify what object on what layer is at the map location, and the tooltip data is queried and returned to the client, which is then displayed. So factors affecting this process will be what is happening on the client machine, the network, and the server at the time the process occurs. The performance seems to change a great deal from very good to unacceptably slow (the user would give up). I find this change strange because other applications (e.g. MapGuide 6.x) run from the same client to the same server are not varying nearly as much. It is also strange in that the initial request for the layout and subsequent requests for layer data are not particularly slow when the tooltips are. Are there any settings which can be altered to improve this? This kind of unreliability could almost rule this technology out in my view. Keith This email and any attached files are confidential and copyright protected. If you are not the addressee, any dissemination of this communication is strictly prohibited. Unless otherwise expressly agreed in writing, nothing stated in this communication shall be legally binding. |
||||||||||||||||
|
Jason Birch
|
In reply to this post by KeithC
Some javascript/style in this post has been disabled (why?)
This would only work if that layer had complete
coverage.
If you wanted "lower" layers to show their tooltips
when they're not covered by higher features (which would be my expected
behaviour) then this wouldn't work.
Jason From: Andy Morsell [mailto:amorsell@...] Sent: Friday, November 17, 2006 10:30 To: users@... Subject: RE: [mapguide-users] RE: Tooltip performance Or, the one single layer to fetch tooltip information for
could be pre-determined by the variables of display priority, selectability, and
whether they have a tooltip definition. Then, only one query would
occur.
Andy From: Jason Birch [mailto:Jason.Birch@...] Sent: Friday, November 17, 2006 10:22 AM To: users@... Subject: RE: [mapguide-users] RE: Tooltip performance Yes, ideally layers with tooltip properties set would
be queried top-down until there is a hit, and then the loop would short
circuit.
Jason From: Andy Morsell [mailto:amorsell@...] Sent: Friday, November 17, 2006 10:19 To: users@... Subject: RE: [mapguide-users] RE: Tooltip performance Why is each FeatureSource for each layer queried when it is
only the top-most layer in the display priority that should display the
tooltip?
Andy From: Trevor Wekel [mailto:trevor.wekel@...] Sent: Friday, November 17, 2006 9:54 AM To: Campbell, Keith A; users@... Subject: [mapguide-users] RE: Tooltip performance Hi Keith,
You are correct with the basic flow of events for
generating the tooltips. The AJAX client sends the map coordinates of the
point along with the map name to the Web Extensions. The Web
Extensions in turn, forwards this information to the Server.
Once at the server, all of the layers in the map are queried to see
if they have any features underneath the point. Since every layer is
queried, the performance will depend on the number of layers in
the Map. Each FeatureSource for each layer will be queried. If
you have a number of layers from external databases, the database will be
queried for each layer.
Feature Service connection pooling and caching may
help. These are controlled by the following settings in serverconfig.ini
and should be accessible from Server Admin.
[FeatureServiceProperties]
DataConnectionPoolSize =
20
DataConnectionPoolExcludedProviders = OSGeo.SDF,OSGeo.SHP DataConnectionPoolEnabled = 1 DataCacheSize = 100 CacheSize = 100 Just as a side note, I think MapGuide 6.x handles tooltip
generation client side. I don't think it goes back to the server so it
will be less affected by server load.
Thanks,
Trevor From: Campbell, Keith A [mailto:keith.campbell@...] Sent: Friday, November 17, 2006 6:53 AM To: users@... Subject: Tooltip performance I'm finding that the performance of the tooltips is varying greatly and I'd like to understand what is going on behind the scenes and therefore what factors are affecting this. Presumably when the cursor s moved over the map, a mouseover event is triggered and this sends the position information and state of the layers is sent back to the server via an xmlhttprequest. The web extensions are used to identify what object on what layer is at the map location, and the tooltip data is queried and returned to the client, which is then displayed. So factors affecting this process will be what is happening on the client machine, the network, and the server at the time the process occurs. The performance seems to change a great deal from very good to unacceptably slow (the user would give up). I find this change strange because other applications (e.g. MapGuide 6.x) run from the same client to the same server are not varying nearly as much. It is also strange in that the initial request for the layout and subsequent requests for layer data are not particularly slow when the tooltips are. Are there any settings which can be altered to improve this? This kind of unreliability could almost rule this technology out in my view. Keith This email and any attached files are confidential and copyright protected. If you are not the addressee, any dissemination of this communication is strictly prohibited. Unless otherwise expressly agreed in writing, nothing stated in this communication shall be legally binding. |
||||||||||||||||
|
Trevor Wekel
|
In reply to this post by KeithC
Some javascript/style in this post has been disabled (why?)
Hi Jason,
Looks as though we only use the selectability property
currently. The routine is shared code with selection
handling.
Trevor From: Jason Birch [mailto:Jason.Birch@...] Sent: Friday, November 17, 2006 11:17 AM To: users@... Subject: RE: [mapguide-users] RE: Tooltip performance Is it just
layers that have had their selectability
property cleared that will be ignored, or will not setting a maptip have the
same effect?
Jason From: Trevor Wekel [mailto:trevor.wekel@...] Sent: Friday, November 17, 2006 10:15 To: Campbell, Keith A; users@... Subject: [mapguide-users] RE: Tooltip performance Hi Keith,
You can also disable selection for layers which do
not require tooltips. If a layer is not selectable, it is not included in
the query.
Thanks,
Trevor From: Trevor Wekel Sent: Friday, November 17, 2006 10:54 AM To: 'Campbell, Keith A'; users@... Subject: RE: Tooltip performance Hi Keith,
You are correct with the basic flow of events for
generating the tooltips. The AJAX client sends the map coordinates of the
point along with the map name to the Web Extensions. The Web
Extensions in turn, forwards this information to the Server.
Once at the server, all of the layers in the map are queried to see
if they have any features underneath the point. Since every layer is
queried, the performance will depend on the number of layers in
the Map. Each FeatureSource for each layer will be queried. If
you have a number of layers from external databases, the database will be
queried for each layer.
Feature Service connection pooling and caching may
help. These are controlled by the following settings in serverconfig.ini
and should be accessible from Server Admin.
[FeatureServiceProperties]
DataConnectionPoolSize =
20
DataConnectionPoolExcludedProviders = OSGeo.SDF,OSGeo.SHP DataConnectionPoolEnabled = 1 DataCacheSize = 100 CacheSize = 100 Just as a side note, I think MapGuide 6.x handles tooltip
generation client side. I don't think it goes back to the server so it
will be less affected by server load.
Thanks,
Trevor From: Campbell, Keith A [mailto:keith.campbell@...] Sent: Friday, November 17, 2006 6:53 AM To: users@... Subject: Tooltip performance I'm finding that the performance of the tooltips is varying greatly and I'd like to understand what is going on behind the scenes and therefore what factors are affecting this. Presumably when the cursor s moved over the map, a mouseover event is triggered and this sends the position information and state of the layers is sent back to the server via an xmlhttprequest. The web extensions are used to identify what object on what layer is at the map location, and the tooltip data is queried and returned to the client, which is then displayed. So factors affecting this process will be what is happening on the client machine, the network, and the server at the time the process occurs. The performance seems to change a great deal from very good to unacceptably slow (the user would give up). I find this change strange because other applications (e.g. MapGuide 6.x) run from the same client to the same server are not varying nearly as much. It is also strange in that the initial request for the layout and subsequent requests for layer data are not particularly slow when the tooltips are. Are there any settings which can be altered to improve this? This kind of unreliability could almost rule this technology out in my view. Keith This email and any attached files are confidential and copyright protected. If you are not the addressee, any dissemination of this communication is strictly prohibited. Unless otherwise expressly agreed in writing, nothing stated in this communication shall be legally binding. |
||||||||||||||||
Willem Schwarte
|
In reply to this post by Trevor Wekel
Some javascript/style in this post has been disabled (why?)
Hmm… I could imagine that somebody
would like tooltips on a layer, but would like the layer not to be selectable. I’m
finding it rather strange that the tooltip is dependent on the selectability of
a layer …. Was this also the case on Mapguide 6.5? (I’m a little in
doubt while typing this… ) Van: Trevor Wekel
[mailto:trevor.wekel@...] Hi Keith, You can also disable selection for
layers which do not require tooltips. If a layer is not selectable, it is
not included in the query. Thanks, Trevor From: Trevor
Wekel Hi Keith, You are correct with the basic flow of
events for generating the tooltips. The Feature Service connection pooling and
caching may help. These are controlled by the following settings in
serverconfig.ini and should be accessible from Server Admin. [FeatureServiceProperties] DataConnectionPoolSize = 20 Just as a side note, I think MapGuide 6.x
handles tooltip generation client side. I don't think it goes back to the
server so it will be less affected by server load. Thanks, Trevor From: Campbell,
Keith A [mailto:keith.campbell@...] I'm
finding that the performance of the tooltips is varying greatly and I'd like to
understand what is going on behind the scenes and therefore what factors are
affecting this. Presumably
when the cursor s moved over the map, a mouseover event is triggered and this
sends the position information and state of the layers is sent back to the
server via an xmlhttprequest. The web extensions are used to identify what
object on what layer is at the map location, and the tooltip data is queried
and returned to the client, which is then displayed. So factors affecting this
process will be what is happening on the client machine, the network, and the
server at the time the process occurs. The
performance seems to change a great deal from very good to unacceptably slow
(the user would give up). I find this change strange because other applications
(e.g. MapGuide 6.x) run from the same client to the same server are not varying
nearly as much. It is also strange in that the initial request for the layout
and subsequent requests for layer data are not particularly slow when the
tooltips are. Are there any settings which can be altered to improve this? This
kind of unreliability could almost rule this technology out in my view. Keith
This email and any attached files are confidential and copyright
protected. If you are not the addressee, any dissemination of this
communication is strictly prohibited. Unless otherwise expressly agreed in
writing, nothing stated in this communication shall be legally binding. |
||||||||||||||||
|
Trevor Wekel
|
In reply to this post by KeithC
Some javascript/style in this post has been disabled (why?)
Ok. I traced this through all three tiers to check
the behaviour. The layers are queried top down until there is a hit and it
does short circuit once it finds one. This could still lead to a lot of
FDO queries if the feature pointed to is at the bottom of the
list.
Trevor From: Jason Birch [mailto:Jason.Birch@...] Sent: Friday, November 17, 2006 11:22 AM To: users@... Subject: RE: [mapguide-users] RE: Tooltip performance Yes, ideally layers with tooltip properties set would
be queried top-down until there is a hit, and then the loop would short
circuit.
Jason From: Andy Morsell [mailto:amorsell@...] Sent: Friday, November 17, 2006 10:19 To: users@... Subject: RE: [mapguide-users] RE: Tooltip performance Why is each FeatureSource for each layer queried when it is
only the top-most layer in the display priority that should display the
tooltip?
Andy From: Trevor Wekel [mailto:trevor.wekel@...] Sent: Friday, November 17, 2006 9:54 AM To: Campbell, Keith A; users@... Subject: [mapguide-users] RE: Tooltip performance Hi Keith,
You are correct with the basic flow of events for
generating the tooltips. The AJAX client sends the map coordinates of the
point along with the map name to the Web Extensions. The Web
Extensions in turn, forwards this information to the Server.
Once at the server, all of the layers in the map are queried to see
if they have any features underneath the point. Since every layer is
queried, the performance will depend on the number of layers in
the Map. Each FeatureSource for each layer will be queried. If
you have a number of layers from external databases, the database will be
queried for each layer.
Feature Service connection pooling and caching may
help. These are controlled by the following settings in serverconfig.ini
and should be accessible from Server Admin.
[FeatureServiceProperties]
DataConnectionPoolSize =
20
DataConnectionPoolExcludedProviders = OSGeo.SDF,OSGeo.SHP DataConnectionPoolEnabled = 1 DataCacheSize = 100 CacheSize = 100 Just as a side note, I think MapGuide 6.x handles tooltip
generation client side. I don't think it goes back to the server so it
will be less affected by server load.
Thanks,
Trevor From: Campbell, Keith A [mailto:keith.campbell@...] Sent: Friday, November 17, 2006 6:53 AM To: users@... Subject: Tooltip performance I'm finding that the performance of the tooltips is varying greatly and I'd like to understand what is going on behind the scenes and therefore what factors are affecting this. Presumably when the cursor s moved over the map, a mouseover event is triggered and this sends the position information and state of the layers is sent back to the server via an xmlhttprequest. The web extensions are used to identify what object on what layer is at the map location, and the tooltip data is queried and returned to the client, which is then displayed. So factors affecting this process will be what is happening on the client machine, the network, and the server at the time the process occurs. The performance seems to change a great deal from very good to unacceptably slow (the user would give up). I find this change strange because other applications (e.g. MapGuide 6.x) run from the same client to the same server are not varying nearly as much. It is also strange in that the initial request for the layout and subsequent requests for layer data are not particularly slow when the tooltips are. Are there any settings which can be altered to improve this? This kind of unreliability could almost rule this technology out in my view. Keith This email and any attached files are confidential and copyright protected. If you are not the addressee, any dissemination of this communication is strictly prohibited. Unless otherwise expressly agreed in writing, nothing stated in this communication shall be legally binding. |
||||||||||||||||
|
Jason Birch
|
In reply to this post by KeithC
Some javascript/style in this post has been disabled (why?)
That seems sub-optimal.
- It's spending extra cycles on layers that don't need to
be queried.
- What happens if I have a layer which is not selectable,
but for which I want to return a maptip?
What would it take to change this?
Jason From: Trevor Wekel [mailto:trevor.wekel@...] Sent: Friday, November 17, 2006 10:34 To: Jason Birch; users@... Subject: RE: [mapguide-users] RE: Tooltip performance Hi Jason,
Looks as though we only use the selectability property
currently. The routine is shared code with selection
handling.
Trevor From: Jason Birch [mailto:Jason.Birch@...] Sent: Friday, November 17, 2006 11:17 AM To: users@... Subject: RE: [mapguide-users] RE: Tooltip performance Is it just
layers that have had their selectability
property cleared that will be ignored, or will not setting a maptip have the
same effect?
Jason From: Trevor Wekel [mailto:trevor.wekel@...] Sent: Friday, November 17, 2006 10:15 To: Campbell, Keith A; users@... Subject: [mapguide-users] RE: Tooltip performance Hi Keith,
You can also disable selection for layers which do
not require tooltips. If a layer is not selectable, it is not included in
the query.
Thanks,
Trevor From: Trevor Wekel Sent: Friday, November 17, 2006 10:54 AM To: 'Campbell, Keith A'; users@... Subject: RE: Tooltip performance Hi Keith,
You are correct with the basic flow of events for
generating the tooltips. The AJAX client sends the map coordinates of the
point along with the map name to the Web Extensions. The Web
Extensions in turn, forwards this information to the Server.
Once at the server, all of the layers in the map are queried to see
if they have any features underneath the point. Since every layer is
queried, the performance will depend on the number of layers in
the Map. Each FeatureSource for each layer will be queried. If
you have a number of layers from external databases, the database will be
queried for each layer.
Feature Service connection pooling and caching may
help. These are controlled by the following settings in serverconfig.ini
and should be accessible from Server Admin.
[FeatureServiceProperties]
DataConnectionPoolSize =
20
DataConnectionPoolExcludedProviders = OSGeo.SDF,OSGeo.SHP DataConnectionPoolEnabled = 1 DataCacheSize = 100 CacheSize = 100 Just as a side note, I think MapGuide 6.x handles tooltip
generation client side. I don't think it goes back to the server so it
will be less affected by server load.
Thanks,
Trevor From: Campbell, Keith A [mailto:keith.campbell@...] Sent: Friday, November 17, 2006 6:53 AM To: users@... Subject: Tooltip performance I'm finding that the performance of the tooltips is varying greatly and I'd like to understand what is going on behind the scenes and therefore what factors are affecting this. Presumably when the cursor s moved over the map, a mouseover event is triggered and this sends the position information and state of the layers is sent back to the server via an xmlhttprequest. The web extensions are used to identify what object on what layer is at the map location, and the tooltip data is queried and returned to the client, which is then displayed. So factors affecting this process will be what is happening on the client machine, the network, and the server at the time the process occurs. The performance seems to change a great deal from very good to unacceptably slow (the user would give up). I find this change strange because other applications (e.g. MapGuide 6.x) run from the same client to the same server are not varying nearly as much. It is also strange in that the initial request for the layout and subsequent requests for layer data are not particularly slow when the tooltips are. Are there any settings which can be altered to improve this? This kind of unreliability could almost rule this technology out in my view. Keith This email and any attached files are confidential and copyright protected. If you are not the addressee, any dissemination of this communication is strictly prohibited. Unless otherwise expressly agreed in writing, nothing stated in this communication shall be legally binding. |
||||||||||||||||
|
Trevor Wekel
|
In reply to this post by KeithC
Some javascript/style in this post has been disabled (why?)
Hi Jason,
It looks as though we will need some API changes (HTTP
Protocol, MgMap) to implement this. Since API changes are involved, should
this be handled as an RFC?
Thanks,
Trevor
From: Jason Birch [mailto:Jason.Birch@...] Sent: Friday, November 17, 2006 11:39 AM To: users@... Cc: Trevor Wekel Subject: RE: [mapguide-users] RE: Tooltip performance That seems sub-optimal.
- It's spending extra cycles on layers that don't need to
be queried.
- What happens if I have a layer which is not selectable,
but for which I want to return a maptip?
What would it take to change this?
Jason From: Trevor Wekel [mailto:trevor.wekel@...] Sent: Friday, November 17, 2006 10:34 To: Jason Birch; users@... Subject: RE: [mapguide-users] RE: Tooltip performance Hi Jason,
Looks as though we only use the selectability property
currently. The routine is shared code with selection
handling.
Trevor From: Jason Birch [mailto:Jason.Birch@...] Sent: Friday, November 17, 2006 11:17 AM To: users@... Subject: RE: [mapguide-users] RE: Tooltip performance Is it just
layers that have had their selectability
property cleared that will be ignored, or will not setting a maptip have the
same effect?
Jason From: Trevor Wekel [mailto:trevor.wekel@...] Sent: Friday, November 17, 2006 10:15 To: Campbell, Keith A; users@... Subject: [mapguide-users] RE: Tooltip performance Hi Keith,
You can also disable selection for layers which do
not require tooltips. If a layer is not selectable, it is not included in
the query.
Thanks,
Trevor From: Trevor Wekel Sent: Friday, November 17, 2006 10:54 AM To: 'Campbell, Keith A'; users@... Subject: RE: Tooltip performance Hi Keith,
You are correct with the basic flow of events for
generating the tooltips. The AJAX client sends the map coordinates of the
point along with the map name to the Web Extensions. The Web
Extensions in turn, forwards this information to the Server.
Once at the server, all of the layers in the map are queried to see
if they have any features underneath the point. Since every layer is
queried, the performance will depend on the number of layers in
the Map. Each FeatureSource for each layer will be queried. If
you have a number of layers from external databases, the database will be
queried for each layer.
Feature Service connection pooling and caching may
help. These are controlled by the following settings in serverconfig.ini
and should be accessible from Server Admin.
[FeatureServiceProperties]
DataConnectionPoolSize =
20
DataConnectionPoolExcludedProviders = OSGeo.SDF,OSGeo.SHP DataConnectionPoolEnabled = 1 DataCacheSize = 100 CacheSize = 100 Just as a side note, I think MapGuide 6.x handles tooltip
generation client side. I don't think it goes back to the server so it
will be less affected by server load.
Thanks,
Trevor From: Campbell, Keith A [mailto:keith.campbell@...] Sent: Friday, November 17, 2006 6:53 AM To: users@... Subject: Tooltip performance I'm finding that the performance of the tooltips is varying greatly and I'd like to understand what is going on behind the scenes and therefore what factors are affecting this. Presumably when the cursor s moved over the map, a mouseover event is triggered and this sends the position information and state of the layers is sent back to the server via an xmlhttprequest. The web extensions are used to identify what object on what layer is at the map location, and the tooltip data is queried and returned to the client, which is then displayed. So factors affecting this process will be what is happening on the client machine, the network, and the server at the time the process occurs. The performance seems to change a great deal from very good to unacceptably slow (the user would give up). I find this change strange because other applications (e.g. MapGuide 6.x) run from the same client to the same server are not varying nearly as much. It is also strange in that the initial request for the layout and subsequent requests for layer data are not particularly slow when the tooltips are. Are there any settings which can be altered to improve this? This kind of unreliability could almost rule this technology out in my view. Keith This email and any attached files are confidential and copyright protected. If you are not the addressee, any dissemination of this communication is strictly prohibited. Unless otherwise expressly agreed in writing, nothing stated in this communication shall be legally binding. |
||||||||||||||||
|
Willem Schwarte
|
Some javascript/style in this post has been disabled (why?)
I would really like it if
this tooltip thing, got its own routines. Then you can just query the top layer
and if this has a tooltip, break from routine, else just query the next, till
you get a tooltip. Most maps will have more
then 10 layers, so it seems a bit overkill to query them all, when you just
want the top layers tooltip… And also don’t let it
depend on the selectability of the layer, you always want to see a tooltip (if
this property is filled). Willem Van: Trevor Wekel
[mailto:trevor.wekel@...] Hi Jason, It looks as though we will need some API
changes (HTTP Protocol, MgMap) to implement this. Since API changes are
involved, should this be handled as an RFC? Thanks, Trevor From:
Jason Birch [mailto:Jason.Birch@...] That seems sub-optimal. - It's spending extra cycles on layers
that don't need to be queried. - What happens if I have a layer which is
not selectable, but for which I want to return a maptip? What would it take to change this? Jason From:
Trevor Wekel [mailto:trevor.wekel@...] Hi Jason, Looks as though we only use the
selectability property currently. The routine is shared code with
selection handling. Trevor From:
Jason Birch [mailto:Jason.Birch@...] Is it just layers that have
had their selectability property cleared that will be ignored, or will not
setting a maptip have the same effect? Jason From:
Trevor Wekel [mailto:trevor.wekel@...] Hi Keith, You can also disable selection for
layers which do not require tooltips. If a layer is not selectable, it is
not included in the query. Thanks, Trevor From:
Trevor Wekel Hi Keith, You are correct with the basic flow of
events for generating the tooltips. The AJAX client sends the map
coordinates of the point along with the map name to the Web
Extensions. The Web Extensions in turn, forwards this information
to the Server. Once at the server, all of the layers in the map
are queried to see if they have any features underneath the
point. Since every layer is queried, the performance will depend on the
number of layers in the Map. Each FeatureSource for each layer
will be queried. If you have a number of layers from external databases,
the database will be queried for each layer. Feature Service connection pooling and
caching may help. These are controlled by the following settings in
serverconfig.ini and should be accessible from Server Admin. [FeatureServiceProperties] DataConnectionPoolSize = 20 Just as a side note, I think MapGuide 6.x
handles tooltip generation client side. I don't think it goes back to the
server so it will be less affected by server load. Thanks, Trevor From:
Campbell, Keith A [mailto:keith.campbell@...] I'm
finding that the performance of the tooltips is varying greatly and I'd like to
understand what is going on behind the scenes and therefore what factors are
affecting this. Presumably
when the cursor s moved over the map, a mouseover event is triggered and this
sends the position information and state of the layers is sent back to the
server via an xmlhttprequest. The web extensions are used to identify what
object on what layer is at the map location, and the tooltip data is queried
and returned to the client, which is then displayed. So factors affecting this
process will be what is happening on the client machine, the network, and the
server at the time the process occurs. The
performance seems to change a great deal from very good to unacceptably slow
(the user would give up). I find this change strange because other applications
(e.g. MapGuide 6.x) run from the same client to the same server are not varying
nearly as much. It is also strange in that the initial request for the layout
and subsequent requests for layer data are not particularly slow when the
tooltips are. Are there any settings which can be altered to improve this? This
kind of unreliability could almost rule this technology out in my view. Keith
This email and any attached files are confidential and copyright
protected. If you are not the addressee, any dissemination of this
communication is strictly prohibited. Unless otherwise expressly agreed in
writing, nothing stated in this communication shall be legally binding. |
||||||||||||||||
Brad Nesom
|
Some javascript/style in this post has been disabled (why?)
I Agree Willem. The tooltips worked quick in mapguide 6.5.
The only other option that would be nice would be to prioritize them separately
from layer display. (sometimes there is a layer displayed on top that makes it
kind of hard to get the tooltip you want). I realize this is always going to be
a contention but if there were a priority you could remove some contention. Brad From: Willem Schwarte
[mailto:willem@...] I would really like it if
this tooltip thing, got its own routines. Then you can just query the top layer
and if this has a tooltip, break from routine, else just query the next, till
you get a tooltip. Most maps will have more then
10 layers, so it seems a bit overkill to query them all, when you just want the
top layers tooltip… And also don’t let
it depend on the selectability of the layer, you always want to see a tooltip
(if this property is filled). Willem Van: Trevor
Wekel [mailto:trevor.wekel@...] Hi Jason, It looks as though we
will need some API changes (HTTP Protocol, MgMap) to implement this.
Since API changes are involved, should this be handled as an RFC? Thanks, Trevor From: Jason
Birch [mailto:Jason.Birch@...] That seems
sub-optimal. - It's spending extra
cycles on layers that don't need to be queried. - What happens if I have
a layer which is not selectable, but for which I want to return a maptip? What would it take to
change this? Jason From: Trevor
Wekel [mailto:trevor.wekel@...] Hi Jason, Looks as though we
only use the selectability property currently. The routine is shared code
with selection handling. Trevor From: Jason
Birch [mailto:Jason.Birch@...] Is it just layers
that have had their selectability property cleared that will be ignored,
or will not setting a maptip have the same effect? Jason From: Trevor
Wekel [mailto:trevor.wekel@...] Hi Keith, You can also disable
selection for layers which do not require tooltips. If a layer is not
selectable, it is not included in the query. Thanks, Trevor From: Trevor
Wekel Hi Keith, You are correct with the
basic flow of events for generating the tooltips. The AJAX client sends
the map coordinates of the point along with the map name to the Web
Extensions. The Web Extensions in turn, forwards this
information to the Server. Once at the server, all of the
layers in the map are queried to see if they have any features
underneath the point. Since every layer is queried, the performance will
depend on the number of layers in the Map. Each FeatureSource
for each layer will be queried. If you have a number of layers from external
databases, the database will be queried for each layer. Feature Service
connection pooling and caching may help. These are controlled by the
following settings in serverconfig.ini and should be accessible from Server
Admin. [FeatureServiceProperties] DataConnectionPoolSize =
20 Just as a side note, I
think MapGuide 6.x handles tooltip generation client side. I don't think
it goes back to the server so it will be less affected by server load. Thanks, Trevor From: Campbell,
Keith A [mailto:keith.campbell@...] I'm finding that the performance
of the tooltips is varying greatly and I'd like to understand what is going on
behind the scenes and therefore what factors are affecting this. Presumably when the cursor s moved over the map, a mouseover event is
triggered and this sends the position information and state of the layers is
sent back to the server via an xmlhttprequest. The web extensions are used to
identify what object on what layer is at the map location, and the tooltip data
is queried and returned to the client, which is then displayed. So factors
affecting this process will be what is happening on the client machine, the
network, and the server at the time the process occurs. The performance seems to change a great deal from very good to
unacceptably slow (the user would give up). I find this change strange because
other applications (e.g. MapGuide 6.x) run from the same client to the same
server are not varying nearly as much. It is also strange in that the initial
request for the layout and subsequent requests for layer data are not
particularly slow when the tooltips are. Are there any settings which can be
altered to improve this? This kind of unreliability could almost rule this
technology out in my view. Keith This email and any attached files are confidential and
copyright protected. If you are not the addressee, any dissemination of this
communication is strictly prohibited. Unless otherwise expressly agreed in
writing, nothing stated in this communication shall be legally binding. |
||||||||||||||||
Butler, Juan P
|
In reply to this post by KeithC
Some javascript/style in this post has been disabled (why?)
I’m also seeing that some symbols
work better than others when it comes to tooltips. I’m not
sure if it’s the positioning of the reference point or what. I
can only get the most basic of symbols to properly display the tooltips in a
consistent and timely manner. Juan Butler - Senior Programmer/Analyst Please note: All mail
sent to and from Pinellas County Government is subject to the Public Records
Law of Florida. From: Brad Nesom
[mailto:kidsmake6@...] I Agree Willem. The tooltips worked quick in mapguide 6.5.
The only other option that would be nice would be to prioritize them separately
from layer display. (sometimes there is a layer displayed on top that makes it
kind of hard to get the tooltip you want). I realize this is always going to be
a contention but if there were a priority you could remove some contention. Brad From: Willem Schwarte
[mailto:willem@...] I would really like it if
this tooltip thing, got its own routines. Then you can just query the top layer
and if this has a tooltip, break from routine, else just query the next, till
you get a tooltip. Most maps will have more
then 10 layers, so it seems a bit overkill to query them all, when you just
want the top layers tooltip… And also don’t let
it depend on the selectability of the layer, you always want to see a tooltip
(if this property is filled). Willem Van: Trevor
Wekel [mailto:trevor.wekel@...] Hi Jason, It looks as though we will
need some API changes (HTTP Protocol, MgMap) to implement this. Since API
changes are involved, should this be handled as an RFC? Thanks, Trevor From: Jason
Birch [mailto:Jason.Birch@...] That seems
sub-optimal. - It's spending extra
cycles on layers that don't need to be queried. - What happens if I have
a layer which is not selectable, but for which I want to return a maptip? What would it take to
change this? Jason From: Trevor
Wekel [mailto:trevor.wekel@...] Hi Jason, Looks as though we
only use the selectability property currently. The routine is shared code
with selection handling. Trevor From: Jason
Birch [mailto:Jason.Birch@...] Is it just layers
that have had their selectability property cleared that will be ignored,
or will not setting a maptip have the same effect? Jason From: Trevor
Wekel [mailto:trevor.wekel@...] Hi Keith, You can also disable
selection for layers which do not require tooltips. If a layer is not
selectable, it is not included in the query. Thanks, Trevor From: Trevor
Wekel Hi Keith, You are correct with the
basic flow of events for generating the tooltips. The AJAX client sends
the map coordinates of the point along with the map name to the Web
Extensions. The Web Extensions in turn, forwards this information
to the Server. Once at the server, all of the layers in the map
are queried to see if they have any features underneath the
point. Since every layer is queried, the performance will depend on the
number of layers in the Map. Each FeatureSource for each layer
will be queried. If you have a number of layers from external databases,
the database will be queried for each layer. Feature Service
connection pooling and caching may help. These are controlled by the
following settings in serverconfig.ini and should be accessible from Server
Admin. [FeatureServiceProperties] DataConnectionPoolSize =
20 Just as a side note, I think
MapGuide 6.x handles tooltip generation client side. I don't think it
goes back to the server so it will be less affected by server load. Thanks, Trevor From: Campbell,
Keith A [mailto:keith.campbell@...] I'm finding that the performance
of the tooltips is varying greatly and I'd like to understand what is going on
behind the scenes and therefore what factors are affecting this. Presumably when the cursor s moved over the map, a mouseover event is
triggered and this sends the position information and state of the layers is
sent back to the server via an xmlhttprequest. The web extensions are used to
identify what object on what layer is at the map location, and the tooltip data
is queried and returned to the client, which is then displayed. So factors
affecting this process will be what is happening on the client machine, the
network, and the server at the time the process occurs. The performance seems to change a great deal from very good to
unacceptably slow (the user would give up). I find this change strange because
other applications (e.g. MapGuide 6.x) run from the same client to the same
server are not varying nearly as much. It is also strange in that the initial
request for the layout and subsequent requests for layer data are not
particularly slow when the tooltips are. Are there any settings which can be
altered to improve this? This kind of unreliability could almost rule this technology
out in my view. Keith This email and any attached files are confidential and
copyright protected. If you are not the addressee, any dissemination of this
communication is strictly prohibited. Unless otherwise expressly agreed in
writing, nothing stated in this communication shall be legally binding. |
||||||||||||||||
|
KeithC
|
In reply to this post by KeithC
Some javascript/style in this post has been disabled (why?)
Hi Trevor,
Thanks for the response.
I've noted that the tooltips are returned in good time in
Studio, but not when the map is viewed in the web browser, the tooltips either
don't display, display after a 'significant' delay, or display the wrong data
(perhaps due to the time lag). I have turned the selectability of a
number of layers off (which I would prefer to display tooltips for but will
perhaps set up labels for instead) and the tooltips are now OK-ish in the
browser also.
Regarding the Feature Service settings, I've changed theses
as follows:-
DataConnectionPoolSize = 100
DataCacheSize = 500 CacheSize = 500 (increased them
fivefold) with no perceivable difference. What would you suggest I change these
to in order to see improved performance?
Regarding the
setting of tooltips, I agree with other comments that this should be set
independently, i.e not based on the layer
selectability.
Keith From: Trevor Wekel [mailto:trevor.wekel@...] Sent: 17 November 2006 18:15 To: Campbell, Keith A; users@... Subject: RE: Tooltip performance Hi Keith,
You can also disable selection for layers which do
not require tooltips. If a layer is not selectable, it is not included in
the query.
Thanks,
Trevor From: Trevor Wekel Sent: Friday, November 17, 2006 10:54 AM To: 'Campbell, Keith A'; users@... Subject: RE: Tooltip performance Hi Keith,
You are correct with the basic flow of events for
generating the tooltips. The AJAX client sends the map coordinates of the
point along with the map name to the Web Extensions. The Web
Extensions in turn, forwards this information to the Server.
Once at the server, all of the layers in the map are queried to see
if they have any features underneath the point. Since every layer is
queried, the performance will depend on the number of layers in
the Map. Each FeatureSource for each layer will be queried. If
you have a number of layers from external databases, the database will be
queried for each layer.
Feature Service connection pooling and caching may
help. These are controlled by the following settings in serverconfig.ini
and should be accessible from Server Admin.
[FeatureServiceProperties]
DataConnectionPoolSize =
20
DataConnectionPoolExcludedProviders = OSGeo.SDF,OSGeo.SHP DataConnectionPoolEnabled = 1 DataCacheSize = 100 CacheSize = 100 Just as a side note, I think MapGuide 6.x handles tooltip
generation client side. I don't think it goes back to the server so it
will be less affected by server load.
Thanks,
Trevor From: Campbell, Keith A [mailto:keith.campbell@...] Sent: Friday, November 17, 2006 6:53 AM To: users@... Subject: Tooltip performance I'm finding that the performance of the tooltips is varying greatly and I'd like to understand what is going on behind the scenes and therefore what factors are affecting this. Presumably when the cursor s moved over the map, a mouseover event is triggered and this sends the position information and state of the layers is sent back to the server via an xmlhttprequest. The web extensions are used to identify what object on what layer is at the map location, and the tooltip data is queried and returned to the client, which is then displayed. So factors affecting this process will be what is happening on the client machine, the network, and the server at the time the process occurs. The performance seems to change a great deal from very good to unacceptably slow (the user would give up). I find this change strange because other applications (e.g. MapGuide 6.x) run from the same client to the same server are not varying nearly as much. It is also strange in that the initial request for the layout and subsequent requests for layer data are not particularly slow when the tooltips are. Are there any settings which can be altered to improve this? This kind of unreliability could almost rule this technology out in my view. Keith This email and any attached files are confidential and copyright protected. If you are not the addressee, any dissemination of this communication is strictly prohibited. Unless otherwise expressly agreed in writing, nothing stated in this communication shall be legally binding. This message has been scanned for viruses by MailControl |
||||||||||||||||
| Free Embeddable Forum Powered by Nabble | Help |
