Unsolved
This post is more than 5 years old
15 Posts
0
1621
March 26th, 2011 23:00
Slow SourceOne message preview
Hi everyone,
We recently implemented S1 in our environment and so far everything appears to be working fine, however there is one annoyance that I can't seem to pinpoint the cause. When previewing messages that were queried via the S1 web search, some if not most emails take in upwards of 30 seconds to display the contents of the email in the preview pane. For example I would conduct a search for some email messages; S1 returns the list of messages, then when I select one of the email messages to preview, my browser (Internet Explorer 8 or Firefox) would sit there stating at the bottom of the browser "Waiting for archive.mycompany.com/preview.aspx.....", and after 20+ seconds the contents of the message finally appear. Yet if I select to view a different message, certain ones will display within a 1 - 2 seconds. By the way, this even happens to messages that have been shortcut by S1 and previewed via Outlook 2010 client with the Offline Cache plugin installed.
Anyone have any ideas why it does this or how this can be fixed? I have even looked at the DocManageService.log in S1 and I can see this 20 second delay recorded.
Gary_Reardon
2 Intern
•
272 Posts
0
March 27th, 2011 06:00
Do you have Cache enable?
Do these messages fall within or outside of the Cache settings?
trapspeed
15 Posts
0
March 27th, 2011 13:00
Where do I find the cache settings for this?
Gary_Reardon
2 Intern
•
272 Posts
0
March 27th, 2011 13:00
Offline Access Client settings.
Location depends on the version on Outlook.
trapspeed
15 Posts
0
March 27th, 2011 14:00
Oh...sorry, to clarify with cache enabled using the Outlook Offline client plugin seems to work ok. I guess with it disabled there is a delay, so that I suppose is expected.
However using the web search and previewing messages still produces quite a bit of a delay. And again, some messages would display the preview within a couple seconds while the rest doesn't appear for about 20 seconds. I could swear that doing web searches and previewing them in EmailXtender was a lot faster than this.
Gary_Reardon
2 Intern
•
272 Posts
0
March 27th, 2011 17:00
Search performance is directly related to having the required storage IOPS on the SQL & Index drives and the appropriate server CPU & Memory resources.
Retrieval performance is the related to Archive storage and Server performance.
Was this implementation configured properly per the Sizing Calculator?
tlarsen1
17 Posts
0
March 29th, 2011 04:00
As to slow performance on the WebSearch remember to check that the workers with Search web services installed should have the polling time set to 2 seconds, as described in the administration guide - page 146 - 147 or thereabout.
Depending on the roles of the worker it is set to either 10 or 2 seconds.
Regards
Thomas
trapspeed
15 Posts
0
March 29th, 2011 10:00
I've set the settings to 2 seconds as you mentioned. The queries do seem to come up a bit faster which is fine but again the previews for the majority come up slowly (about 20 seconds for some). Does S1 cache the contents of the messages you query, or does it put a call out to retrieve the contents of the message you select?
RKatwal
2 Intern
•
600 Posts
0
March 29th, 2011 16:00
Greetings,
SourceOne search will only have the search results cached in the Search DB but not the messages. Messages are retrieved on demand when a user will select a message.
When a user will select a message search server will send request, this message will be unpacked to a temp location on the worker that got the request and will be displayed in the preview.
This process requires call to SQL to find which message is in which volume, later individual message needs to be unpacked from the EMX file or retrieved from Message Center. Once the individual message is retrieved and unpacked in temp location it is displayed.
I hope this explains.
Thanks,
Rajan