Version 3.0 Beta Test FeedBack

hi,

i installed pb 3.01. and i notice that portal rules work now. but what i although notice is that wp3 process goes to 100 cpu load on different pages of my portal not all.

maybee the css merge is the problem ? how can i disable it via config ?

thanks jens

hi john,

in my case the process never go back to idle mode. it consume 100 % cpu load and the page will never be shown in browser. :(

jens

I just installed it on my localhost clone and all of my styling, and menu disapeared - not good.

Using FireFox and Web Developer the only css visable is from and external source for a bit of code from AddThis.com that I use for bookmarking.

However in PB's cached directory there are 2 merged css files and they appear to have the contents of the correct files in them.

If you need to troubleshoot this I can arrange access via email

----

On a seperate note is MATCHING a URL regex. does IF MATCH agingsafely.com and REPLACE WITH www.AgingSafely.com work for on URL or all non-www URLs?

/Dave

hi john,

i notice the high cpu load although when no portal rule is configured

jens

Ok, i just installed new version Snapsis.DNN.PageBlaster_3.0.1_Install.zip and now i see a module in Admin > PageBlaster page and it has a textbox and a GO button.

When viewing this module settings it has relation with Search Results module i guess. Am i right?

Ismet,
You should be seeing a PageBlaster Admin that looks like the Configure screen when you put the module on a page. 
Have you tried un-installing and re-installing?  I'll get that CSS fixed in the next build.

Jens,
Maybe there is something wrong with the CSS replacements I am doing to make the paths in the CSS file point to the right place. 

I am attaching the PageBlaster.dll to this post.  If you turn on Debug to the trace file in the Snapsis.PageBlaster.config file then youc can trace the starting and completion times of each CSS file processed.  I have also compiled this in Debug mode so there should be good info in the trace file.

If you want to attach your CSS files for a page that is experiencing this high CPU problem then I'll run them through a regex checker to see if there is a problem with my pattern.

Last but not least. The DLL that is attached to this post corrects the problem of the CSS path not getting formatted correctly.

I have some questions about merging css. Typically DNN pages have 6-7 linked css files. Many are common to each page and should be cached in the browser after the first page view.

With your merging of them into a single unique css file doesn't all this code get loaded for each page view?  If so - where does the performance improvement come from?

BTW with the number of little floppy icons that PB has maybe a title-tag is in order so that you get a hint of what each is going to do.

/Dave

It is usually true that these files are cached in the local browser cache, but what usually happens is that they are not given an expires header, so you will still see several get requests on every page view which return a 304 response (meaning that the requested resource has not been modified).

Limiting the number of http requests is a great way to optimize performance.  If you haven't checked out the YSlow Plugin for FireFox yet then I highly recommend it.

Here is what YSLow says about Http Requests

What I have done is put all the CSS Files into one, but it is still linked so it still gets cached on the browser.
I also have a static file handler in PageBlaster now that is not enabled by default, but if you enable it for CSS & JSS then it will allow you to do all the same caching, compression, and replacements in those files that you can do in the html Page.

To enable the Static File Handler for CSS and/or JS you will need to setup your application in IIS so that requests for CSS and/or JS are sent to the ASP.Net framework.
I have attached a couple images to this post to show how that is done.  Along with the IIS Setup you will also need the following line added to your web.config in the httpHandlers section.

<httpHandlers><addverb="*"path="*.css,*.js"type="Snapsis.HttpModules.PageBlaster.StaticFileHandler, Snapsis.HttpModules.PageBlaster"/>

ok,

the new dll complete destrory my webdesign. seems that the css didn´t load correct. the 100 cpu load still stands but i have generate a trace file.

jens

Wow YSLow is interesting. How many of its suggestions do you implement?  As for the redirecting od CSS and JS to ASP, do you think that ISP will be willing?

When I run YSLow agains my site I get several A's and several F's. Ill have to dig a little deeper but I not sure how I can implement many of the solutions. They would appear to be built into how DNN implements things.

/DaveS

That is correct, if you are caching the page then it will only be updated if the page expires or if you manually refresh it. When you are logged in it is not cached by default so maybe that is enough (especially if the data is mainly watched by the site owner). If you wanted it to update every hour then you could set the interval that low, but i wouldn't recommend that unless you have a highly viewed page where the updates become more important.

One good thing about caching is that the more traffic you have the lower you can set the interval and still get tremondous gains.

Also, if there is a module that uses Ajax to show dynamic data then you could have a cached page that "magically" gets updated in the background.

I would recommend putting a who's online module on a page other than your home page if you really want it to be updated very frequently.