Memory Settings Running on a MacMini

Tim Nevels (4/25/14 7:48PM)
Tim Nevels (4/25/14 7:49PM)
Tim Nevels (4/25/14 7:50PM)
Jack Des Bouillons (4/27/14 11:46PM)
Joshua Fletcher (4/28/14 6:12AM)
Tim Nevels (4/30/14 10:38PM)
Thomas Maul (5/1/14 9:59AM)
Tim Nevels (5/1/14 5:29PM)


Tim Nevels (4/25/14 7:48 PM)

On Apr 25, 2014, at 6:52 PM, Jack Des Bouillons wrote:

color><param>00000,0000,DDEE/param>AAnd the desired cache value would
be...?
/color>

You have 8GB of RAM. So max out the cache setting and use 2300MB. The
absolute max for 4D v13 32bit on Mac OS X is 2384MB. I like round it
off to 2300MB.

If you set it to anything higher than 2384MB you will get an error
message when you launch 4D Server.

Tim

Tim Nevels (4/25/14 7:49 PM)

On Apr 25, 2014, at 6:52 PM, Joshua Fletcher wrote:

color><param>00000,0000,DDEE/param>TThis is a single instance, right?

Step 1: uncheck "Calculation of adaptive cache".
Step 2: type in your desired cache value.

There is absolutely no reason to use adaptive cache for a single
deployment. =A0More to the point, adaptive cache is just confusing
for a
single deployment and provides no benefit.
/color>

Finally a sane response from 4D on using the adaptive cache setting.

You know, the default setting should be to NOT use adaptive cache.
Maybe in v15 this change will be made. Adaptive cache should be an
advanced setting, not the default setting.

As Jack says?=80 my opinion.

Tim

Tim Nevels (4/25/14 7:50 PM)

On Apr 25, 2014, at 6:52 PM, Joshua Fletcher wrote:

color><param>00000,0000,DDEE/param>TTom Benedict already gave the best
answer to this question. In case you missed it:

http://kb.4d.com/resources/inug?msgid=GmailId145918414b4f910b

Based on your current settings, start with 512 MB since that won't
change anything.
/color>

Are you serious? He's said his data file is over 10GB and he has a Mac
Mini with 8GB or RAM and the machine is only used for 4D Server.

Why screw around testing what is "best"? Just max out the cache at
2300MB and be done with it. How could having a 512MB cache be a good
starting place? The end result will be to max out the cache at 2300MB.

What am I missing here?

Tim

Jack Des Bouillons (4/27/14 11:46 PM)

I must not have explained my situation on my first post...the setting
of 512
was WRONG...for years, going back to 2003/2004, I set the max cache at
2048.
On the day I made my posting, we were having some unexpected behavior
on our
system, and I happened to check the settings...and there I saw 512 or
both
min and max...

It had been so long since I even looked at this setting, I had
forgotten
what my usual settings were...hence my post to the NUG to jog my
memory.

Everything seems to be working fine, so I think I'll just keep
everything as
is. ?I do appreciate everyone's help in this matter.

Jack des Bouillons

On 4/27/14 9:12 PM, "Joshua Fletcher" <JFletcher@... wrote:

color><param>00000,0000,DDEE/param>HHabit. Make as few changes as
possible and test the result. ?Disabling
adaptive cache is one change. ?Altering the cache size is another
change.
If something goes wrong, which change was at fault?

His current cache is 512 MB so, as I said, setting it to 512 won't
change
anything&copy;the implication being you can then start evidence-based
testing
as Tom suggested.

Also, setting the maximum value of ~2300 MB on OS X means you're
leaving
only ~1200 MB for everything else. ?Is that enough? ?I don't know,
I've
never seen the system in question, so I would never suggest going
straight
for the maximum size.

Anecdote: I have a single-user app for image processing that *easily*
consumes ~4 GB, so I set the cache small.

This is why I think evidence-based analysis is "the best".

-Josh
/color>

Joshua Fletcher (4/28/14 6:12 AM)

Habit. Make as few changes as possible and test the result. ?Disabling
adaptive cache is one change. ?Altering the cache size is another
change.
If something goes wrong, which change was at fault?

His current cache is 512 MB so, as I said, setting it to 512 won't
change
anything?=A0the implication being you can then start evidence-based
testing
as Tom suggested.

Also, setting the maximum value of ~2300 MB on OS X means you're
leaving
only ~1200 MB for everything else. ?Is that enough? ?I don't know,
I've
never seen the system in question, so I would never suggest going
straight
for the maximum size.

Anecdote: I have a single-user app for image processing that *easily*
consumes ~4 GB, so I set the cache small.

This is why I think evidence-based analysis is "the best".

-Josh

--
Josh Fletcher
Technical Account Manager
4D, Inc.

On 4/25/14, 5:50 PM, "Tim Nevels" <timnevels@... wrote:

color><param>00000,0000,DDEE/param>AAre you serious? He's said his
data file is over 10GB and he has a Mac
Mini with 8GB or RAM and the machine is only used for 4D Server.

Why screw around testing what is "best"? Just max out the cache at
2300MB
and be done with it. How could having a 512MB cache be a good starting
place? The end result will be to max out the cache at 2300MB.

What am I missing here?

Tim
/color>

Tim Nevels (4/30/14 10:38 PM)

On Apr 30, 2014, at 8:26 PM, James Brown wrote:

color><param>00000,0000,DDEE/param>WWe have a new Mac Pro with 32GB
ram. We currently use a cache of 1600MB. (20GB datafile). I thought
that the total limit was 2000MB, so having the cache set at 1600MB
would leave 400MB for the application itself. Am I wrong?
/color>
Yes, you are wrong. :)

color><param>00000,0000,DDEE/param>SSo, just to confirm, I can
increase the cache to 2300MB and 4D Server won?=80&ocirc;t crash or
anything?
The 2300MB limit is just for the cache itself, the program itself does
not use this?

(Running Mavericks 10.9.2, 4D v13.5)
/color>
This is how I understand it works. I could be wrong. Josh or Miyako
please correct me. It's easy to be wrong when you are talking about
memory limits and 4D 32bit. It is a complicated topic.

The total addressable memory on Mac OS X for 4D Server 32bit is
defined by an unsigned longint -- 4,294,967,295 bytes, or 4096MB, or
4GB. 4D has sent a limit of 2384MB for the data cache. That leaves
about 1712MB for use by the 4D Server program and processes. Depending
on how many users are connected and how many processes each user is
running and memory needs of each process, 1712MB may be plenty or not
enough.

I have 4 4D Servers v13.4 running on Mac OS X 10.6.8 with the data
cache set at 2300MB. The most active 4D Server in this group has
around 50 users connected with about 250 processes. I've had no
issues. No crashes. Say each process needs 2MB of memory -- I don't
know, I'm just making a reasonable guess. That would be about a 500MB
memory load just for the processes. =A0Still leaves another 1200MB of
memory for 4D Server to use for whatever it needs.

So you will have to evaluate your situation. But for me, 2300MB data
cache has been working fine on Mac OS X 10.6.8 and 4D Server v13.4.

color><param>00000,0000,DDEE/param>PPS. Is version 14.1 64-bit on OS X?
/color>
No it is not. There is no news of when 64bit 4D Server for Mac OS will
be released.

Tim

Thomas Maul (5/1/14 9:59 AM)

color><param>00000,0000,DDEE/param>
/color><color><param>8826F,0000,8219/param>TThere is no news of when
64bit 4D Server for Mac OS will be released.
/color>TThere is:
http://www.4d.com/news/4d-v14-r2-continuous-delivery.html

?=85=A0
Future ?=82=B3R?=82=B2 releases will include, in addition to
new commands and
functionalities, major changes, such as a 64-bit version of 4D Server
for
Mac OS X, support for gigabytes of cache usage, or the first
appearance of
a totally new 4D Write?=85=A0

?=85=A0

We target for 2014 to deliver 4D v14 R2 (May), 4D v14 R3 and there is
even
a good chance for 4D v14 R4?=85=A0
So if you order a new Mac Mini to be used for 4D Server these days, go
for
16 MB.

Tim Nevels (5/1/14 5:29 PM)

On May 1, 2014, at 4:59 PM, Thomas Maul wrote:

color><param>FFC79,0365,0771/param>TThere is no news of when 64bit 4D
Server for Mac OS will be released.
/color><color><param>00000,0000,DDEE/param>TThere is:
http://www.4d.com/news/4d-v14-r2-continuous-delivery.html

Future R releases will include, in addition to new commands and
functionalities, major changes, such as a 64-bit version of 4D Server
for
Mac OS X, support for gigabytes of cache usage, or the first
appearance of
a totally new 4D Write?=85

We target for 2014 to deliver 4D v14 R2 (May), 4D v14 R3 and there is
even
a good chance for 4D v14 R4
So if you order a new Mac Mini to be used for 4D Server these days, go
for
16 GB.
/color>
A very interesting comment Thomas. You don't come right out and say in
so many words "there will be a v14 version of 4D Server that will be
64bit for Mac OS coming in 2014". =A0But is sure sounds like that is
what you are saying based on your quotes from v14 Continuous Delivery.
:)

Good news! Very good news!!

Tim

Reply to this message

Summary created 5/1/14 at 10:16PM by Intellex Corporation

Comments welcome at: feedback@intellexcorp.com