compdigit44
asked on
Sharepoint 2010 and IIS Compression
I have read the enabling compressing in IIS can help with SharePoint performance. I am not an IIS or SharePoint experts and wanted to get other opinions on this as to the pro's / con's
ASKER
I 100% agree with you my problem is that I have not skilled in SharePoint and my manager has asked me to fix sharepoint for the last admin who set it up and knew less than I did.
I know you can use things like developer dashboard but this is still above me skill set yet. I have a feeling the problem with out slow performance is from poor coding and web parts.
We are also using SSL with a Netscaler and not offload and is setup for secure connections from the client to the netscaler and from the netscaler to the back end servers.
Back to compression. I am guessing this would need to be done on all WFE's and the server level, is a IISreset required?
I know you can use things like developer dashboard but this is still above me skill set yet. I have a feeling the problem with out slow performance is from poor coding and web parts.
We are also using SSL with a Netscaler and not offload and is setup for secure connections from the client to the netscaler and from the netscaler to the back end servers.
Back to compression. I am guessing this would need to be done on all WFE's and the server level, is a IISreset required?
ASKER
I 100% agree with you my problem is that I have not skilled in SharePoint and my manager has asked me to fix sharepoint for the last admin who set it up and knew less than I did.
I know you can use things like developer dashboard but this is still above me skill set yet. I have a feeling the problem with out slow performance is from poor coding and web parts.
We are also using SSL with a Netscaler and not offload and is setup for secure connections from the client to the netscaler and from the netscaler to the back end servers.
Back to compression. I am guessing this would need to be done on all WFE's and the server level, is a IISreset required?
I know you can use things like developer dashboard but this is still above me skill set yet. I have a feeling the problem with out slow performance is from poor coding and web parts.
We are also using SSL with a Netscaler and not offload and is setup for secure connections from the client to the netscaler and from the netscaler to the back end servers.
Back to compression. I am guessing this would need to be done on all WFE's and the server level, is a IISreset required?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
We already had Microsoft SharePoint Risk Assessment and out SharePoint servers. 2x WFE's one Apps and a cluster DB are well over powered for our small environment.
-Yes access is sluggish internally and externally.
-Our WFE's are load balanced through a Citrix Netscaler which uses SSL our all sharepoint connections.
-I am not a developer but trying my best here what is the best way to see if slow page loads is from web parts or other poor coding.
I have read that something called a "closed" web part can cause problems
-Yes access is sluggish internally and externally.
-Our WFE's are load balanced through a Citrix Netscaler which uses SSL our all sharepoint connections.
-I am not a developer but trying my best here what is the best way to see if slow page loads is from web parts or other poor coding.
I have read that something called a "closed" web part can cause problems
Developer dashboard would be, what gives you the clue, if a part of the site makes trouble. At least you can see, if there are elements, which load very slow and which elements these are.
There is no tool, what tells you about bad webparts or bad coding, this is only a very subjective feeling, so you need some technical values to decide, if there is something on the site, which lets it loading slowly. Even it can be just a bad combination of items, i.e. RSS feed can be very slow as they depent from servers in the internet.
Closed webparts can be there, yes. Whith Sharepoint Designer you can see them and possibly remove them, or better to recover them by changing the tag, which hides them and then to delete them from Sharepoint "Edit page". If people are not aware about some webparts, they sometimes "close" them instead of deleting them. Than means, they are not deleted, only invisible.
There is no tool, what tells you about bad webparts or bad coding, this is only a very subjective feeling, so you need some technical values to decide, if there is something on the site, which lets it loading slowly. Even it can be just a bad combination of items, i.e. RSS feed can be very slow as they depent from servers in the internet.
Closed webparts can be there, yes. Whith Sharepoint Designer you can see them and possibly remove them, or better to recover them by changing the tag, which hides them and then to delete them from Sharepoint "Edit page". If people are not aware about some webparts, they sometimes "close" them instead of deleting them. Than means, they are not deleted, only invisible.
Are you struggling with sharepoint performance?
In my opinion IIS compression would be something you look into after having looked at the more obvious avenues e.g. hardware, sharepoint architecture etc
Not easy to say do it/don't do it
If you have problems then look to the traditional problem solving areas first.