search for: tunable

Hi Guys, My users are reporting some issues with memory on our lustre 1.8.1 clients. It looks like when they submit a single job at a time the run time was about 4.5 minutes. However, when they ran multiple jobs (10 or less) on a client with 192GB of memory on a single node the run time for each job was exceeding 3-4X the run time for the single process. They also noticed that the swap space

...it: 622232 kB Committed_AS: 43236 kB PageTables: 468 kB VmallocTotal: 696312 kB VmallocUsed: 856 kB VmallocChunk: 695416 kB /dev/slabinfo slabinfo - version: 2.1 # name <active_objs> <num_objs> <objsize> <objperslab> <pagesperslab> : tunables <limit> <batchcount> <sharedfactor> : slabdata <active> rpc_buffers 8 8 2048 2 1 : tunables 24 12 8 : slabdata 4 4 0 rpc_tasks 8 15 256 15 1 : tunables 120 60 8 : slabdata 1 1 0 r...

Starting with 3.7 rc1, my workstation seems to loose ram. Up until (and including) 3.6, used-(buffers+cached) was roughly the same as sum(rss) (taking shared into account). Now there is an approx 6G gap. When the box first starts, it is clearly less swappy than with <= 3.6; I can''t tell whether that is related. The reduced swappiness persists. It seems to get worse when I update

I'm currently hacking on CTDB's IP takeover/failover code. For Samba 4.6, I would like to rationalise the IP takeover-related tunable parameters. I would like to know if there are any users who set the values of these tunables to non-default values. The tunables in question are: DisableIPFailover Default: 0 When set to non-zero, ctdb will not perform failover or failback. Even if a node fails while hol...

...d the thread that was pointed to on lkml. ROTFLMAO. *Real* UNIX addressed these problems long ago. I guess the "Gurus" suffer from NIH (Not Invented Here) syndrome. Given a "general purpose" system, tunability is a must. UNIX, as delivered by USL in such examples as Sys V, had tunables that let admins tune to their needs. A single "swappiness" value is woefully inadequate. Among the tunables were how much memory for cache, how much for buffers, how much for X/Y/Z, high and low water marks for all sorts of memory related stuff and a very valuable attribute bit for exec...

Hi, I want to know the tunable parameters in ext2/ext3 filesystem. What are the tunable parameters and what is the effect of tuning those parameters on filesystem? Thanks and Regards, Dilip Kumar Nutakki Software Engineer UNISYS Global Services India, 135/1, Purva Premier ,Residency Road, Bangalore-560025, Ph: +91 80 4159 494...

The documentation for 5.2 indicates the glock_purge tunable parameter is present for GFS in its example output from `gfs_tool gettune`. However, I just upgraded a 5.1 system to 5.2 and everything looks good except for the mysterious absence of the glock_purge parameter. Any ideas as to why this tunable which I was looking forward to getting is missing? -...

The RX buffer size determines the memory consumption of the vsock/virtio guest driver, so we make it tunable through a module parameter. The size allowed are between 4 KB and 64 KB in order to be compatible with old host drivers. Suggested-by: Stefan Hajnoczi <stefanha at redhat.com> Signed-off-by: Stefano Garzarella <sgarzare at redhat.com> --- include/linux/virtio_vsock.h | 1 + net/...

On 2019/5/13 ??6:05, Jason Wang wrote: > > On 2019/5/10 ??8:58, Stefano Garzarella wrote: >> The RX buffer size determines the memory consumption of the >> vsock/virtio guest driver, so we make it tunable through >> a module parameter. >> >> The size allowed are between 4 KB and 64 KB in order to be >> compatible with old host drivers. >> >> Suggested-by: Stefan Hajnoczi <stefanha at redhat.com> >> Signed-off-by: Stefano Garzarella <sgarzare at redh...

Author: danice Repository: /hg/zfs-crypto/gate Revision: 23a634d2405ff5c1e9e1ecf200708d8159060505 Log message: 6364698 Add /etc/system tunable support for XMITS'' UPPER_RTRY counter registers Files: update: usr/src/uts/sun4u/io/pci/pci_space.c update: usr/src/uts/sun4u/io/pci/pcisch.c update: usr/src/uts/sun4u/sys/pci/pci_pbm.h update: usr/src/uts/sun4u/sys/pci/pci_space.h update: usr/src/uts/sun4u/sys/pci/pcisch.h

On 2019/5/10 ??8:58, Stefano Garzarella wrote: > The RX buffer size determines the memory consumption of the > vsock/virtio guest driver, so we make it tunable through > a module parameter. > > The size allowed are between 4 KB and 64 KB in order to be > compatible with old host drivers. > > Suggested-by: Stefan Hajnoczi <stefanha at redhat.com> > Signed-off-by: Stefano Garzarella <sgarzare at redhat.com> I don't see...

On 2019/5/10 ??8:58, Stefano Garzarella wrote: > The RX buffer size determines the memory consumption of the > vsock/virtio guest driver, so we make it tunable through > a module parameter. > > The size allowed are between 4 KB and 64 KB in order to be > compatible with old host drivers. > > Suggested-by: Stefan Hajnoczi <stefanha at redhat.com> > Signed-off-by: Stefano Garzarella <sgarzare at redhat.com> I don't see...

Hello, I think this needs a few more eyes: http://lists.freebsd.org/pipermail/freebsd-scsi/2009-January/003782.html In short, writes are slow, likely do to the write-cache being enabled on the controller. The sysctl used in 6.x to turn the cache off don't seem to be in 7.x. Thanks, Charles ___ Charles Sprickman NetEng/SysAdmin Bway.net - New York's Best Internet - www.bway.net

Hi, As a next question to my building this server. I'm nogt able to get a full verbose dmesg. Probably because the kernelbuffer for it is too small. I know there used to be a kernel option to increase it. But I can not find it with the setting in NOTES or any other place I looked.... Is it still there? Thanx, --WjW

On Wed, 25 Apr 2018, James Bottomley wrote: > On Wed, 2018-04-25 at 17:22 -0400, Mikulas Patocka wrote: > > > > On Wed, 25 Apr 2018, David Rientjes wrote: > > > > > > Do we really need the new config option???This could just be > > > manually? tunable via fault injection IIUC. > > > > We do, because we want to enable it in RHEL and Fedora debugging > > kernels,?so that it will be tested by the users. > > > > The users won't use some extra magic kernel options or debugfs files. > > If it can be enabled v...

On Wed, 25 Apr 2018, James Bottomley wrote: > > > Do we really need the new config option???This could just be > > > manually? tunable via fault injection IIUC. > > > > We do, because we want to enable it in RHEL and Fedora debugging > > kernels,?so that it will be tested by the users. > > > > The users won't use some extra magic kernel options or debugfs files. > > If it can be enabled v...

...the tx routine . Turn on tx interrrupts per transmit ring. . Have a single NIC-wide interrupt shared for all tx ring''s transmit completion events, and turn that interrupt ON. . Have a high water mark/low water mark for triggering the reclaiming from the transmit routine. . Some internal tunables to choose one or a combination of the approaches above (how to detect the right time to change the tunables'' setting?) I am wondering what has been the experience of folks on this alias with the performance gain or penalty from the various choices above, or if they used different way...

We have 10 SuperMicro PDSMi+ 5015M-MTs that are panic'ing every few days. This started shortly after upgrade from 6.2-RELEASE to 6.3-RELEASE with freebsd-update. Other than switching to a debugging kernel, a little sysctl tuning, and patching with freebsd-update, they are stock. The debugging kernel was built from source that is also being patched with freebsd-update. These systems are

...be described in the manual page so that users would > know that export OPENBLAS_NUM_THREADS=1 is a solution. There isn't much R can do about the behaviour of the BLAS, because there is no standard interface to set the number of threads. Some BLASes (like ATLAS) don't even offer it as a tunable number at all [*]. A system administrator could link the installation of R against FlexiBLAS [**], provide safe defaults in the environment variables and educate the users about its tunables [***], but that's a choice just like it had been a choice to link R against a parallel variant of OpenB...

Hi, I read some articles on solarisinternals.com like "ZFS_Evil_Tuning_Guide" on http://www.solarisinternals.com/wiki/index.php/ZFS_Evil_Tuning_Guide . They clearly suggest to disable cache flush http://www.solarisinternals.com/wiki/index.php/ZFS_Evil_Tuning_Guide#FLUSH . It seems to be the only serious article on the net about this subject. Could someone here state on this