Logo 
Search:

Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Memory Leaks, SPTimer, restarttimer

  Asked By: Dontae    Date: Jun 16    Category: Sharepoint    Views: 2749

I've seen on this board several mentions to memory leaks caused by
OWSTIMER.exe.

I'm finally getting around to putting this on my servers.

I understand that you can control the service from the command line with

net stop WSSTimerV3

There is an stsadm command restarttimer.

I don't have this command available. I also read this is part of the
"Administration Extension Download for SharePoint"

I've found an "Extension Pack 2.0" Does that mean WSS 2.0?

I'm looking for a way to schedule the restart. Should I just put this in
system scheduler?

Also along the same lines, do I need to make sure all my application
pools have a recycle time? What are some guidelines for how often this
should be?

Share: 

 

5 Answers Found

 
Answer #1    Answered By: Dara Hobbs     Answered On: Jun 16

It is called 'Barracuda Application Extension download  for SharePoint'
on the premium content download site.

You can schedule  it on server, and it can reset all the servers  in the
farm. Also added to the tool is the ability to manage some individual
timer jobs.

#2. I would leave the default nightly reset of app pools, and schedule a
warmup of your aspx pages so the JIT compile doesn't frustrate your
users.

blogs.msdn.com/.../697044.aspx

Good luck, and keep the great posts coming! You seem to have more
answers than questions.

 
Answer #2    Answered By: Abhinivesh Suvarna     Answered On: Jun 16

Is it better to stagger the nightly app pool reset so each app pool
gives the prior one time  to start up?

In the case of staggering them, would you suggest I run a warmup script
for each app pool right after its scheduled cycle, or wait until all app
pools have cycled and run JIT warmup all at once in the middle of the
night?

 
Answer #3    Answered By: Micheal Knight     Answered On: Jun 16

Frankly its neither here nor there so long as you warm up as soon as reasonably
practicable

Personally I would recycle  them 1/2 an hour apart starting at 1am and then warm
up at 6am but it is only an intranet so isn't really in use in the early hours

 
Answer #4    Answered By: Yvonne Rodriquez     Answered On: Jun 16

The ServerXMLHTTP object utilized by the warmup script won't work for https
sites.

support.microsoft.com/default.aspx\
080

It is a little frustrating that I have to create an alternate access mapping for
each app so I can hit it from http.

I was thinking of asking our network guys to add the URL's to the load
balancer heartbeat.

If it is hitting these pages constantly it shouldn't be a big resource strain
for cached pages, and it will always be the first to discover that an app pool
has recycled.

Does anybody have feedback for this?

 
Answer #5    Answered By: Elisha Abbott     Answered On: Jun 16

Yes. Many are creating an AAM and warming them up via HTTP internally.

 
Didn't find what you were looking for? Find more on Memory Leaks, SPTimer, restarttimer Or get search suggestion and latest updates.




Tagged: