User talk:Petelomax: Difference between revisions
→Use of Factorization Wheels in Sieves: replay on slow compilation...
GordonBGood (talk | contribs) (→Use of Factorization Wheels in Sieves: replay on slow compilation...) |
|||
Line 64:
:::: I can understand that compilation speed is a concern and in fact is already slow on my low end machine - about 30 seconds for a `-c` pass of a basic test program, where my machine is over twice as slow as yours given the speed to run the extensible generator as a benchmark. But some improvements such as making designated builtin functions inline and (possibly) adding the slightly more sophisticated power of two multiply/divide shouldn't take much time.
::::: It has only just occurred to me: 30s is indeed quite a long time & I'll bet what's happening is your a.v. is kicking in and giving the resultant exe a good once-over. After a few goes it should get bored with that. --[[User:Petelomax|Pete Lomax]] ([[User talk:Petelomax|talk]]) 16:47, 29 December 2018 (UTC)
:::::: Yes, I have experienced AV slowing expected performance before on occasion, and it seems you are right in this instance: Windows Defender (on Windows 10) is doing some kind of extensive scan triggered every time I start a compile cycle (no matter how trivial) and can't really get started until that scan is finished, which is probably the majority of the 30 seconds. It wasn't expected that AV would be triggered on every invocation.--[[User:GordonBGood|GordonBGood]] ([[User talk:GordonBGood|talk]]) 06:45, 31 December 2018 (UTC)
:::: "performance issues on subscripting" I suppose means indexing of sequences? Not inlined? bounds checking is slow? Bounds checking can't be optionally turned off?
| |||