[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: 64-bit

From: Nathan Kidd <nathan-svn_at_spicycrypto.ca>
Date: 2005-12-19 23:08:20 CET

Stefan Küng wrote:
> Ok, so asm is much faster. But let's be realistic here. OpenSSL is used
> for https connections. And even if you check out big working copies, the
> CPU usage never goes above 10% - the bottleneck is always the network.
> Ok, let's assume you have a GB network connection, even in that case,
> the bottleneck wouldn't be the CPU usage but the harddisk, because you
> usually check out many smaller files which need to be written to the disk.

Sorry, I jumped into this purely from an academic angle of, "is OpenSSL
significantly faster with asm than with C + optimizing compiler?".
Looking at the broader context, what you say above is certainly true.

> I'm not sure, but I don't think it's possible to load a 32-bit dll into
> a 64-bit process. So OpenSSL must be 64-bit too for TSVN.
> Because, the shell extension must be 64-bit for the shell to load it.
> That leads to the apr dll's to be 64-bit. And I don't think those dll's
> get different names for 64/32-bit builds. So if those dll's are 64-bit,
> TortoiseProc and all others must be 64-bit too. Which again leads to
> OpenSSL to be 64-bit too.

We've had the same problem and come to the same conclusion here -- it
must be 64-bit.


To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue Dec 20 00:04:50 2005

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.