On Sun, Jun 20, 2010 at 1:46 PM, Alan W. Irwin
wrote:
>
> So for mingw32-make our wine startup latencies are essentially identical
> (near 150 ms) and substantially worse than the Windows numbers (30 ms) and
> much worse than the Linux numbers (~1 ms). "make" startup latency matters
> for builds
On 2010-06-20 11:16+1000 Jeff Zaroyko wrote:
On Sun, Jun 20, 2010 at 12:50 AM, Alan W. Irwin
wrote:
Thanks very much Jeff, for providing some independent timing numbers for
startup latency which are an order of magnitude (!) smaller than mine.
So what is different about our wine platforms to c
On Sun, Jun 20, 2010 at 12:50 AM, Alan W. Irwin
wrote:
> Thanks very much Jeff, for providing some independent timing numbers for
> startup latency which are an order of magnitude (!) smaller than mine.
> So what is different about our wine platforms to cause that huge
> difference? More below.
>
Thanks very much Jeff, for providing some independent timing numbers for
startup latency which are an order of magnitude (!) smaller than mine.
So what is different about our wine platforms to cause that huge
difference? More below.
On 2010-06-19 12:55+1000 Jeff Zaroyko wrote:
Windows:
$ time
On Sat, Jun 19, 2010 at 11:00 AM, David Gerard wrote:
> On 18 June 2010 20:12, Alan W. Irwin wrote:
>
>> That would be a most interesting comparison. In computer terms 150 ms is an
>> absolutely enormous time that allows something like 150 million (!)
>> operations to occur on modern PC's. So I
On 18 June 2010 20:12, Alan W. Irwin wrote:
> That would be a most interesting comparison. In computer terms 150 ms is an
> absolutely enormous time that allows something like 150 million (!)
> operations to occur on modern PC's. So I would be surprised if Microsoft
> Windows required that long
Hi Paul:
Thanks for your ideas on reducing the command startup latency.
On 2010-06-18 10:48+0300 Paul Chitescu wrote:
Alan,
Try to keep the wineserver initialized and running - for example keep a
cmd.exe or notepad or something idle (in the same WINEPREFIX).
I tried that by running
wine cmd
On Friday 18 June 2010 03:05:08 am Alan W. Irwin wrote:
> On 2010-06-17 17:07-0400 Mike Kaplinskiy wrote:
>
> > On Thu, Jun 17, 2010 at 4:35 PM, Alan W. Irwin
> >> The issue is that Wine builds of software take roughly a factor of 5
longer
> >> than the equivalent Linux builds. This issue appear
On 2010-06-17 17:07-0400 Mike Kaplinskiy wrote:
On Thu, Jun 17, 2010 at 4:35 PM, Alan W. Irwin
The issue is that Wine builds of software take roughly a factor of 5 longer
than the equivalent Linux builds. This issue appears to be caused mostly by
command startup latency. [...]
I find the comm
f.net); and the Linux Brochure Project
> (lbproject.sf.net).
> __________________
>
> Linux-powered Science
> __
>
> -- Forwarded message --
> Date: Sat, 12 Jun 2010 14:10:31 -0700 (PDT)
> From: Alan W. Irwin
> To: wine-us.
_
Linux-powered Science
__
-- Forwarded message --
Date: Sat, 12 Jun 2010 14:10:31 -0700 (PDT)
From: Alan W. Irwin
To: wine-us...@winehq.org
Subject: Re: [Wine] Speed/latency issues for development in a Wine environment
On 2010-06-11 18:09-0700 A
11 matches
Mail list logo
