First access to server extremely slow

[Franz Leu]

Hi,

 

We have updated the svn server to the latest from Collabnet and moved it to a new server (WinServer 2012 R2).

Since then, after some time (minutes) not accessing the server or a local copy, showing a repo in repo-browser or showing a log on a local copy takes about a minute for the first access. After that time, it always is successful and works very snappy until a certain time without access to the server.

I’ve tried with tortoise 1.9.3.21038-x64 as well as with an older 1.7.10.23359-x64, both on W7-X64.

 

Any idea what is wrong with our new setup?

Thanks

[Franz Leu]

Sorry, typo before. This ist he correct version:

TortoiseSVN 1.9.3, Build 27038 - 64 Bit , 2015/12/13 11:53:16

[Stefan Küng]

Since it's only the first access that's slow, it might be a DNS problem:
once the ip of the server url has been resolved, it is cached in the OS
and subsequent accesses are therefore instant.

You could use a network tool like WireShark to monitor the traffic and
check where exactly it stalls.

Stefan


--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest interface to (Sub)version control
/_/ \_\ http://tortoisesvn.net

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3163610

To unsubscribe from this discussion, e-mail: [users-un...@tortoisesvn.tigris.org].

[Franz Leu]

DNS is not the issue. Shows the same effect if DNS is not involved (direct IP used). We are not using https.

I logged with WireShark and found a delay of a minute in the server response whereas there is no delay in subsequent accesses.

For the delayed access, the Collabnet server log shows 2 entries in the access_log but none in the subversion_log for the first access time and shows in both after the minute delay.

It looks as if apache is responding but needs to somehow “wake up” subversion in the background first.

 

Btw: How do I respond to the very same thread?

I never get an email to respond on and can’t find an option on google groups nor on tigris.

[Stefan Küng]

On 08.03.2016 11:47, Franz Leu wrote:
> DNS is not the issue. Shows the same effect if DNS is not involved
> (direct IP used). We are not using https.

If you're not using https, then you should also check virus scanners -
they don't like non-encrypted connections and often interfere.

> I logged with WireShark and found a delay of a minute in the server
> response whereas there is no delay in subsequent accesses.
>
> For the delayed access, the Collabnet server log shows 2 entries in the
> access_log but none in the subversion_log for the first access time and
> shows in both after the minute delay.
>
> It looks as if apache is responding but needs to somehow “wake up”
> subversion in the background first.

It doesn't need to "wake up" anything: the modules are usually already
loaded. And even if they're not, loading a module takes almost no time.

But this isn't really an issue with TSVN as the logs show: it's the
server that responds way too late.
So you should ask for help on either the svn users list or ask Collabnet
for help since you're using their server setup.

> Btw: How do I respond to the very same thread?
>
> I never get an email to respond on and can’t find an option on google
> groups nor on tigris.

you can subscribe to the list on tigris, or reply directly on the tigris
forum (there's a "reply" link, not a button so it's not very obvious,
but it's there).

Stefan

--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest interface to (Sub)version control
/_/ \_\ http://tortoisesvn.net

------------------------------------------------------

http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3164873

[Franz Leu]

Problem solved :-)
It was LDAP authentication, Connection Pool TTL.
Default is set to 'never' (empty) in Collabnet SVNedge whereas the Windows server has a default timeout of 15 minutes.
Setting 900 in Collabnet SVNedge advanced settings solves the issue.

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3166441

[sch...@gmail.com]

Am Freitag, 18. März 2016 09:05:33 UTC+1 schrieb Franz Leu:
> Problem solved :-)
> It was LDAP authentication, Connection Pool TTL.
> Default is set to 'never' (empty) in Collabnet SVNedge whereas the Windows server has a default timeout of 15 minutes.
> Setting 900 in Collabnet SVNedge advanced settings solves the issue.
>

Had the same issue here and setting the Connection Pool TTL indeed solved the problem. Thanks, Markus