Below...
On Wed, 2004-04-14 at 10:30, Anthony Green wrote:
On Tue, 2004-04-13 at 15:08, Jonathan Pryor wrote:
AOT (or pre-JITing) assemblies is not as useful as you'd think. It has
two primary effects:
- Reduce memory requirements, as memory doesn't need to be allocated
for the
No, he is not.
YOu can run
mono -O=shared my.exe
or, if you would like to aot:
mono -O=shared --aot my.exe
However, as miguel stated earlier, the need for shared code is very
rare. What shared means here is that the same code can be used by
multiple appdomains (look that up if you are not
On Wed, 2004-04-14 at 19:47, Jonathan Pryor wrote:
Below...
On Wed, 2004-04-14 at 10:30, Anthony Green wrote:
On Tue, 2004-04-13 at 15:08, Jonathan Pryor wrote:
AOT (or pre-JITing) assemblies is not as useful as you'd think. It has
two primary effects:
- Reduce memory
Hello,
Because you didn't mention the key advantage that you get from
AOT-compiled shared libraries: saving memory from sharing library code
between processes. You're only two points were about saving time and
memory from not having to JIT compile code.
Ah, that is correct, and I had at
On Tue, 2004-04-13 at 15:08, Jonathan Pryor wrote:
AOT (or pre-JITing) assemblies is not as useful as you'd think. It has
two primary effects:
- Reduce memory requirements, as memory doesn't need to be allocated
for the JITed code
- Decrease startup time, as (again) the JITing
Hello,
snip/
Interestingly, my installation of mono (from debian sid) doesn't even
come with its own libraries AOT'd. I'd have thought that you'd get the
best performance by AOT'ing *all* the libraries, including (and
especially) the low-level platform ones such as System.dll and
Below...
On Tue, 2004-04-13 at 14:55, Stuart Ballard wrote:
snip/
Interestingly, my installation of mono (from debian sid) doesn't even
come with its own libraries AOT'd. I'd have thought that you'd get the
best performance by AOT'ing *all* the libraries, including (and
especially) the
7 matches
Mail list logo
