ABD in managed PWise

RE: ABD in managed PWise

Steve Cocchi — Thu, 02 Jul 2015 19:47:50 GMT

Unfortunately I don't have much more to offer since this isn't really an area I work within... I would suggest branching off this particular topic as a new thread on the MicroStation forum to see if any additional input is available.

RE: ABD in managed PWise

ChrisRevuelta — Thu, 02 Jul 2015 01:56:28 GMT

I see that reference to Darius and other links but none really explain anything...

" Let say setting it to MS_Memory_FREELIMIT = 100,700
100,700 -> 100 means that x32 bit program will start lock memory 2GB – 100 = 1,900 GB RAM (it can be set to 200). 700 mean how much RAM memory is installed minus from Operating System programs."

What means "will start lock memory" ? What is the impact if any on ABD? Any definitive answer ? I mean you guys wrote this program...

RE: ABD in managed PWise

Steve Cocchi — Wed, 01 Jul 2015 17:54:37 GMT

The best reference to MS_MEMORY_FREELIMIT that I've found is in the second post here:
communities.bentley.com/.../98803

I think Darius' explanation is fairly clear. Well, as clear as things can be when working with memory allocation in Windows. :-)

In regards to Lock Pages in Memory, the machine where ABD is installed and running (the local machine) is where the variable would be set, since that's where the memory is being consumed. That isn't to say that the integration server can't make use of the additional memory (?), it's just not where ABD itself will be using those resources.

RE: ABD in managed PWise

ChrisRevuelta — Wed, 01 Jul 2015 12:07:31 GMT

To clarify, when using ABD through Projectwise, on which computer the "lock pages in memory" is accessed by the application? Is it on the local or on the integration server?

RE: ABD in managed PWise

ChrisRev — Sat, 27 Jun 2015 07:03:59 GMT

Yes understand about the lock pages in memory, what i would like to know is what is the correct setup for MS_MEMORY_FREELIMIT, the default always being 50/150... or perhaps those number make no difference whatsoever? (which is my belief but i would like to be sure)... the maximum value is 2000 anyway, after which it will always revert to the default values....any reasons?

RE: ABD in managed PWise

Steve Cocchi — Fri, 26 Jun 2015 14:10:58 GMT

Hi Chris,
Cool, I would take that as a positive. :) Matching up permissions seemed like the right thing to do since PW managing the cached data (workspace + DGNs) could potentially conflict between client and server - it was really just a guess on my part but I'm glad that helped to narrow the scope.

Regarding the "lock pages in memory" environment variable, it was designed to extend the available memory for 32bit ABD (via MicroStation) on x64 systems (assuming the memory is available). While certainly not the same as native 64bit, it can give some processes a little extra bump in resources.

RE: ABD in managed PWise

ChrisRevuelta — Wed, 24 Jun 2015 15:42:16 GMT

Thanks Steve, I think that is right. Although I was logged on my computer with a local windows profile with admin rights and "lock pages in memory..." enabled, I was logged on the datasource (on integration server) with a domain profile.

The moment I logged on the computer with the same domain profile as PW - which I should do anyway - problem disappeared.

I haven't yet checked what are the user rights assignments on the server but maybe the answer is there... ?

In any case, not sure these "free limits" have any impact on performance, it's such an old question that seem to me unanswered to this day - but at least it's kinda satisfying to not get the message "...cannot use all the memory in your system etc..."

RE: ABD in managed PWise

Steve Cocchi — Tue, 23 Jun 2015 15:25:49 GMT

I'm honestly not sure, and I don't believe I've come across this before, but is it possible that PW/managed workspace is overriding permissions levels in the process of checking out the file to the local cache folder?