visual studio - Is there a performance impact by turning on LARGEADDRESSAWARE? -

-

i keen know how /largeaddressaware switch works , cannot find implementation details.

can describe happening when switch used , consequences (aside allowing process access more memory)?

i have run simple benchmark using slam++ library on venice, sphere , 100k datasets:

dataset |  time x86 | time x86 /largeaddressaware |   time x64  venice | bad_alloc |                 4276.524971 | 300.315826 sec  sphere |  2.946498 |                    3.605073 |   1.727466 sec    100k | 46.402400 |                   50.196711 |  32.774384 sec

all times in seconds. there have - performance toll can substantial. doing blas operations, accelerated using sse, , whole thing quite memory bound. note peak memory usage on venice in x86 on 3.5 gb (i believe can 4 gb in x64 system), in x64 bit under 4.3 gb. other datasets use less memory, below 2 gb.

in case of x86 /largeaddressaware on venice, t seemed os wants keep of >2 gb in paging file, although memory usage jumped >3 gb when data accessed - cost may stem aggressive paging. also, there advantage arithmetic operations in x64 on x86 (the program can use registers, etc.), why ordinary x86 slower x64 on small datasets.

this measured on machine 2x amd opteron 2356 se , 16 gb of 667 mhz ddr2, running windows server 2003 x64.

on windows 7, intel core i7-2620m, 8 gb 1333 mhz ddr3 machine:

dataset |  time x86 | time x86 /largeaddressaware |   time x64  venice | bad_alloc |                  203.139716 | 115.641463 sec  sphere |  1.714962 |                    1.814261 |   0.870865 sec    100k | 18.040907 |                   18.091992 |  13.660002 sec

this has quite similar behavior, x64 faster x86, , /largeaddressaware slower (although not slower in previous case - depends on cpu or on os).


Comments

Post a Comment

Popular posts from this blog

c# - How Configure Devart dotConnect for SQLite Code First? -

-
can configure following sample code ? when run following code, error : no entity framework provider found ado.net provider invariant name 'devart.data.sqlite' setting in machine.config <system.data> <dbproviderfactories> <add name="dotconnect sqlite" invariant="devart.data.sqlite" description="devart dotconnect sqlite" type="devart.data.sqlite.sqliteproviderfactory, devart.data.sqlite, version=4.6.287.0, culture=neutral, publickeytoken=09af7300eec23701" /> </dbproviderfactories> </system.data> after add below block code in app.config <?xml version="1.0"?> <configuration>   <configsections> <!-- more information on entity framework configuration, visit http://go.microsoft.com/fwlink/?linkid=237468 --> <section name="entityframework" type="system.data.entity.internal.configfile.entityframeworksection, entit...
Read more

c++ - Clear the memory after returning a vector in a function -

-
i have function processes , stores lot of data in , returns results vector of class. amount of data stored in function tremendous , want clear storage memory of function after finished job. necessary (does function automatically clear memory) or should clear memory function? update: vector<customers> process(char* const *filename, vector<int> id) { vector<customers> list_of_customers; (perform actions) return list_of_customers; } variables defined locally within function automatically released @ end of function scope. destructors objects called, should free memory allocated objects (if objects coded correctly). example of such object std::vector . anything you've allocated new must have corresponding delete release storage. try avoid doing own allocation , use raii instead, i.e. containers or smart pointers.
Read more

erlang - Saving a digraph to mnesia is hindered because of its side-effects -

-
updated the digraph library in erlang implements data type side-effectful. each operation on data type saves new state in ets table -- instead of returning altered version of itself, more common in functional languages. the problem usage perspective, impedes effort store or pass around state in convenient way requiring me first "collect" state before can start juggle around. the closest solution have seen far serializer/deserializer , these have drawback tied current structure of digraphs instead of operating on abstract type -- prevents future proof solution. update pascal pointed out serializer utilizes interface of digraph, , hence eliminates drawback mentioned above. better, albeit still inconvenient, see no better alternative. what recommendation on how store digraphs? should go different data type altogether? thanks. i not sure understand concern. fact digraph stored in ets transparent in user interface, might want chnge either exchange digr...
Read more