Embedded Resource Pros/Cons

3 posts, 0 answers
  1. Adam
    Adam avatar
    177 posts
    Member since:
    Oct 2012

    Posted 08 Jan 2008 Link to this post

    We are having an internal debate as to whether or now we should deploy the Prometheus controls with UseEmbeddedScripts and UseEmbeddedSkins enabled. It would be much faster to deploy with it turned on, because otherwise we would have to go through and change the setting on each of the controls and then move the skins and scripts out to the server. Opponents to the using embbeded resources are claiming the following as concerns:

    1. Compressibility of the CSS/JS files,

    2. When/how/if things are cached client side. (IF is the operative word?)

    3. How a load balancer/load balancing situation would help/hurt

    Can you provide any information as to how performance is affected by using embedded resources versus using static resources for the Prometheus controls?


  2. Rob Houck
    Rob Houck avatar
    21 posts
    Member since:
    Jul 2003

    Posted 08 Jan 2008 Link to this post

    I'm also thinking about this. I've read (here on telerk's site) that embedded resources aren't always the most performant way to go. 


    Someone else may have a better understanding of the ASP.net architecture, but I would believe that embedded resources would be slower than a normal request -- since they're being fed thru the ASP.net ISAP filters.. and are not able to be fulfilled via the IIS HTTP (now in Kernel!) requests. (Thus, also not able to be cached, compressed, etc.)
  3. Basel Nimer
    Basel Nimer avatar
    94 posts
    Member since:
    Oct 2009

    Posted 05 May 2010 Link to this post

    link is not active anymore

    can Telerik confirm any performance issues related to embedding resources?

    does embedding prevent client side caching of JS, CSS and image files?

Back to Top