Re: D3/Linux Linux swap file usage
- From: Dale <dale_benedict@xxxxxxxxxxxxxx>
- Date: Thu, 30 Aug 2007 11:47:20 -0700
I'm not concerned that swap is actually happening. I expect swap to
be used. As per the install guide on page 119, the manual states that
"FlashBASIC applications transfer their memory requirements to the
Unix side of shared memory, and to the Unix swap space."
What mostly concerns me, is that the used swap only grows in size, and
never (at least in my observations) lowers. Just before the :files to
do a restore of the system the swap used was over 85%. The swap usage
basically started out at about 4% and is currently at 9.6%
shpstat shows only a quarter of the shared program space used. So we
aren't pushing that space to the limit.
Donno??!?!
I'll keep monitoring the stats and see if I can spot anything.
Dale
On Aug 30, 10:01 am, Tony Gravagno
<address.is.in.po...@xxxxxxxxxxxxxxxxxxxxxx> wrote:
Glen's right. This will happen with the "core" setting high and with
"basic" set to zero when you're using FlashBASIC. It's been a while
but the rule of thumb is something like this:
Example: 1GB of RAM
Double that and create 2GB of swap
RAM allocation about 50% to D3 and 50% to OS = 512MB to D3
If using FlashBASIC, split D3 memory, so:
core = 412MB, basic = 100MB
The documentation in D3 is pretty good about describing this and might
be different from what I'm saying here but these are rough numbers.
So just shutdown D3, change the numbers, then start D3 again. You can
make some changes to pick0 with D3 still up, like adding tape devices,
but the result of changing memory on the system when it's up could be
a weird set of some users getting the new settings and existing users
getting the old settings - not good.
On the other hand you could be looking at a release-specific issue
with the D3 flusher consuming memory and flowing into swap. If the
above doesn't work, first apply all monitor patches for D3 7.2 (an old
release which of course prompted 7.3, 7.4, and 7.5...), then you
should check to ensure that the flusher is working at all. If you
didn't experience massive data loss on a reboot then I'd think the
flusher is fine. If it doesn't look like the flusher itself is
working then you will have to check with RD. If you're concerned
about cost, just think of all the money you've been saving to-date in
maintenance fees and just bit the bullet. ;)
HTH bud
T
"GlenB" wrote:
Check the memory core size in /usr/lib/pick/pick0. You may need to add more
RAM or reduce the pick0 memory specs in order to avoid swapping. I had a
similar problem when allocating too much available RAM to D3. After throwing
in more memory, the swap usage dropped to zero.
Glen
"Dale" wrote
I have a D3/Linux 7.2.1 system that I did a complete restore on a
couple of weeks ago. Before the shutdown to do the reload of files,
the box was using over 85% of the 2GB swap space. After restarting
the system and getting users back on line, the swap usage was around
90MB and has been growing slowly ever since. The swap usage is now
over 200MB.
.
- Follow-Ups:
- Re: D3/Linux Linux swap file usage
- From: Tony Gravagno
- Re: D3/Linux Linux swap file usage
- References:
- D3/Linux Linux swap file usage
- From: Dale
- Re: D3/Linux Linux swap file usage
- From: GlenB
- Re: D3/Linux Linux swap file usage
- From: Tony Gravagno
- D3/Linux Linux swap file usage
- Prev by Date: Re: D3/Linux Linux swap file usage
- Next by Date: Re: D3 Background process - new linux
- Previous by thread: Re: D3/Linux Linux swap file usage
- Next by thread: Re: D3/Linux Linux swap file usage
- Index(es):
Relevant Pages
|
|