My application suffer performance problems on retreiving large datafields through a webservice. The situation is as follow:
I have created a Datatype using the umbraco user control wrapper. To store the data I chose the database datatype "Ntext".
In this field I am storing textstrings that go up to 6000 characters.
This data I retreive trough a webservice, using following code: (stripped down a bit)
[WebMethod(EnableSession = true)]
public DisplayObject getRoute(int routeObjectId,int routeInfoId, int zoomLevel)
{
Node n = new Node(routeObjectId);
string route = n.GetProperty("route").Value;
InfoTag it = new InfoTag();
it.RouteString = route;
it.Id = n.Id.ToString();
dobj.AddTag(it);
}
As you can see. Nothing fancy about that. However.. if I call this method from my javascript there are some weird differences in performance.
Rendertime according Firebug significant increases with the textstring length:
Response time for a request length of 1368 bytes is 720ms
Respones time for a request length of 5345 bytes is 4.7 seconds!
Here is where I come to question the Umbraco api. It seems that the code line "string route = n.GetProperty("route").Value;" causes this unwanted increase of response time.
Anyone experience with this problem and retreiving large datafields?
Thank you for your reply Simon. However that topic doesn't provide a solution. Maybe needless to say but I'm using current latest stable version 4.7.0 of umbraco.
According my theory the slowness is either to blame on umbraco api, but rather on MsSQL engine not performing well on nText datatype which according some sources is deprecated. Changing the datatype to nVarchar was resulting in some nice errors. So I simply decided to write the value to a file on updating in the backend and reading the contents again from file in the frontend.
You shouldn't use the backend Node for this.. This is calling a database. In Umbraco you also have a node object which lives in the NodeFactory namespace which gets it's data from the published xml file. This one is fast and I recomend that you use this Node object instead of the one you currently use.
Below you see a snippet. This is how you can access the published content in Umbraco. It's readonly and really fast. Replace id and propertyalias with your own values
//Create Node 1234 is the id of the node umbraco.NodeFactory.Node node = new umbraco.NodeFactory.Node(1234);
string value = node.GetProperty("yourbigDataField").Value;
Umbraco very slow on retreiving large data field.
Dear community,
My application suffer performance problems on retreiving large datafields through a webservice. The situation is as follow:
I have created a Datatype using the umbraco user control wrapper. To store the data I chose the database datatype "Ntext".
In this field I am storing textstrings that go up to 6000 characters.
This data I retreive trough a webservice, using following code: (stripped down a bit)
[WebMethod(EnableSession = true)] public DisplayObject getRoute(int routeObjectId,int routeInfoId, int zoomLevel) { Node n = new Node(routeObjectId); string route = n.GetProperty("route").Value; InfoTag it = new InfoTag(); it.RouteString = route; it.Id = n.Id.ToString(); dobj.AddTag(it); }As you can see. Nothing fancy about that. However.. if I call this method from my javascript there are some weird differences in performance.
Rendertime according Firebug significant increases with the textstring length:
Hi Mathijs,
You're not the only one thinking GetProperty is slow, see this:
http://our.umbraco.org/forum/developers/api-questions/5647-GetProperty-on-a-member-object-slow
I don't know if it is a common problem though (old post), but if no one has looked into it, the problem persists...
Thank you for your reply Simon. However that topic doesn't provide a solution. Maybe needless to say but I'm using current latest stable version 4.7.0 of umbraco.
Ok guys. Solved it as following.
According my theory the slowness is either to blame on umbraco api, but rather on MsSQL engine not performing well on nText datatype which according some sources is deprecated. Changing the datatype to nVarchar was resulting in some nice errors. So I simply decided to write the value to a file on updating in the backend and reading the contents again from file in the frontend.
Hi Mathijs,
You shouldn't use the backend Node for this.. This is calling a database. In Umbraco you also have a node object which lives in the NodeFactory namespace which gets it's data from the published xml file. This one is fast and I recomend that you use this Node object instead of the one you currently use.
Cheers,
Richard
Hi Richard,
I'm not quite following you. Could you give a code example of what you mean?
Sure,
Below you see a snippet. This is how you can access the published content in Umbraco. It's readonly and really fast. Replace id and propertyalias with your own values
Cheers,
Richard
Yeah I've already tried that. Believe it or not, same slowness!
is working on a reply...