Hi everyone,

I was just wondering if you could try an experiment?

Startup wine (with winecfg) and time how long it takes to get the window appear - first time, and then again (after it has been cached).

If you could post some detail about your system too - OS, HDD type, CPU that would be very helpful.

Here are mine:
OS: Ubuntu Studio 14.04
HDD: 500GB 3.5" SATA-III 6GB/s HDD 7200RPM 16MB CACHE
CPU: AMD A6-3670

Winecfg startup: initial: 26s. subsequent: 3.5s

So, I am very interested in whether this is abnormally slow. I have been in discussion with a developer about a program he is writing that is dependent on wine startup time, and on his system it is 3s initial, and almost instant on subsequent runs. He thought there may be something wrong with my setup. I'm not sure!

Thanks in advance!

James

OS: Debian Sid
HDD: OCZ Agility3 SSD
CPU: AMD FX-8120
wine-1.6.2

Initial: ~20s
Subsequent: ~4s

Just used my watch to get the times so no great accuracy.

1 members found this post helpful.

OS: Slackware 14.1
HDD: 750GB 2.5" SATA 3Gb/s HDD 7,200rpm 16MB buffer
CPU: AMD E-450 APU with Radeon HD 6320 Graphics
Wine 1.7.24

Initial: ~41s
Subsequent: ~3s

This is a fairly slow laptop computer, though it's not very old.

1 members found this post helpful.

Thanks for this! Really helpful! These are within the kind of realm of what I expected. It would be nice to maybe have a couple more replies just to get a bit more of a sample.

On older sample:

OS: Slackware 12.1
HDD: SATA 1TB
CPU: Pentium M 1.7Ghz (Laptop), 2GB RAM
Wine 1.1.34

Initial = 4 sec.
Repeat = 2 sec.

Same machine after reboot, Firefox and a few terminals open.

OS: Slackware -current (14.1+)
HDD: SATA 1TB
CPU: Pentium M 1.7Ghz (Laptop), 2GB RAM
Wine 1.6.1

Initial <4 sec.
Repeat 2.sec.

Interesting data point. Big spread between my sample and others on initial startup - wonder why?

1 members found this post helpful.

OS: Gentoo ~amd64
HDD: 120GB Corsair Force 3 SSD
RAM: 16GB DDR3-1333
CPU: Phenom II X6 1055T

First startup with non-existent .wine folder: 9 seconds
second startup: <1 second

1 members found this post helpful.

Very interesting.. Any idea what might be causing the differences here? It doesn't seem to be particularly due to differences in system speed. I thought it could be due to differences in HDD access times - on my current system, I have everything on 1 massive 400GB partition (having done lots of small partitions for many years). Maybe that makes a difference?

I might try hand-rolling a recent version of wine to see if that speeds things up.

Anyway, it seems it is very hard to predict what a "normal" startup time for wine is! Maybe <1min?

James

OS: CentOS
CPU: AMD Sempron 2600+
HD: 40GB IDE Seagate
RAM: 1.1GB
Time to launch Notepad in Wine 1.2: 7 sec (with OpenOffice and Opera running)

1 members found this post helpful.

Same specs as above, this time I've done it in RAM, on a SSD and on a mechanical disk:
RAM:
Initial: 6s
Second Run: <1s

SSD:
Initial: 8s
Second Run: <1s

HDD:
Initial: 9s
Second Run: <1s

So it seems to me that access times and data rate only play a minor role and most of the time is spent with actually configuring a clean prefix.

1 members found this post helpful.

I tested mine again last night and realised I hadn't noticed the errors due to not finding something to do with Gnome keyring -- I can't install the component to see whether this makes much difference because it's not compatible with the 64 bit version (one of the problems of running Sid).
I also have very bad sound in WINE and limited output device choices.
In short, I'm not sure whether my WINE setup works at all.

1 members found this post helpful.