10 More Discussions You Might Find Interesting
1. AIX
I have a IBM Power9 server coupled with a NVMe StorWize V7000 GEN3 storage, doing some benchmarks and noticing that single thread I/O (80% Read / 20% Write, common OLTP I/O profile) seems slow.
./xdisk -R0 -r80 -b 8k -M 1 -f /usr1/testing -t60 -OD -V
BS Proc AIO read% IO Flag IO/s ... (8 Replies)
Discussion started by: c3rb3rus
8 Replies
2. AIX
Greetings,
i'm wondering if there is a way to determine minimum memory requirement for AIX kernel and OS functions? We use memdetails script from perfpmr package to see actual memory allocation, for example like this:
===========================================================================... (5 Replies)
Discussion started by: dzodzo
5 Replies
3. AIX
For some reason, my AIX 5.2 box has become slow in accepting telnet requests from others boxes. Windows, times out the connection, whereas, Unix it will wait for the AIX to display the login. I connect and it respawns back and says connected, but then sits and wait for what seems forever to get the... (5 Replies)
Discussion started by: mrmurdock
5 Replies
4. AIX
Dears i want to have a clear view about this tuning parameters and what they related to FS or Oracle , and how to figure the percentage of them .
maxperm%
maxclient%
v_pinshm = 1
lgpg_regions = 0
lpgp_size = 0 (3 Replies)
Discussion started by: thecobra151
3 Replies
5. AIX
Dear friends. can anybody suggest me what to be considered in order to achieve maximum performance of AIX on which DB2 will be installed
Thanks is advance :) (1 Reply)
Discussion started by: Vit0_Corleone
1 Replies
6. AIX
Hello,
On Aix 5.2, we changed the parameters tcp_keepinit, tcp_keepintvl and tcp_keepidle with the no command.
tunrestore -R is present in inittab
in the directory /etc/tunables we can clearly see the inclusion of parameters during reboot, including the file lastboot.log
... (0 Replies)
Discussion started by: dantares
0 Replies
7. AIX
How to do Performance monitoring and tuning in AIX. (2 Replies)
Discussion started by: AIXlearner
2 Replies
8. UNIX for Advanced & Expert Users
Hi
I am trying to investigate a disk performance issue, and we are not seem to be hitting the right direction in our analysis.
This is a FC disk running on USP1000 HDS system. The application is an IO intensive application, but our opinion is that it is not performing due to perceived disk... (1 Reply)
Discussion started by: theerthan
1 Replies
9. UNIX for Advanced & Expert Users
Can only root do this, or can other users too? if other users can, do they have to be given permission, and if so, is there a file or something that stores this?
Thanks. (4 Replies)
Discussion started by: JamesByars
4 Replies
10. AIX
I swapped out 2 72 gb disk drives for 2 146 gb drives, both of which spin at 15k.
Are there any I/O parameters I should modify or can modify to get the most out of the new disks?
Thanks,
Mike M. (1 Reply)
Discussion started by: gravy26
1 Replies
ESHCONFIG(8) BSD System Manager's Manual ESHCONFIG(8)
NAME
eshconfig -- configure Essential Communications' HIPPI network interface
SYNOPSIS
eshconfig [-estx] [-b bytes] [-c bytes] [-d filename] [-i usecs] [-m bytes] [-r bytes] [-u filename] [-w bytes] [interface]
DESCRIPTION
eshconfig is used to configure device-specific parameters and download new firmware to the Essential Communications RoadRunner-based HIPPI
network interface. The interface is very sensitive to the DMA performance characteristics of the host, and so requires careful tuning to
achieve reasonable performance. In addition, firmware is likely to change frequently, which necessitates a reasonably easy way to update
that firmware.
Available operands for eshconfig:
-b bytes
Adjust the burst size for read (by NIC of host memory) DMA.
-c bytes
Adjust the burst size for write (by NIC of host memory) DMA.
-d filename
Filename for file to download into NIC firmware. This must be a file in the standard Essential format, with :04 preceding every
line, and a tag line at the end indicating the characteristics of the firmware file.
-e Write data to EEPROM. Normally, setting tuning parameters will only persist until the system is rebooted. Setting this parameter
ensures that the changes will be written to EEPROM.
-i usecs
Interrupt delay in microseconds.
-m bytes
Minimum number of bytes to DMA in one direction (read or write) before allowing a DMA in the other direction. Tuning this prevents
one direction from dominating the flow of bytes, and artificially throttling the NIC.
-r bytes
Bytes before DMA starts for read (from host to NIC). This controls how soon the DMA is triggered; until this many bytes are
requested, the DMA will not begin.
-s Show statistics for the HIPPI NIC. Repeat the option to suppress non-zero statistics.
-t Show current tuning parameters on the host.
-u filename
Name of file to which the NIC firmware should be uploaded. Not currently supported.
-w bytes
Number of bytes required before write (from NIC to host) DMA is started. Until this many bytes are ready to be written, the DMA will
not start.
-x Reset the NIC. This is necessary for the HIPPI-FP support, as ifconfig(8) will no longer physically reset the NIC when the inter-
faces goes up and down.
Only the super-user may modify the configuration of a network interface.
DIAGNOSTICS
Messages indicating the specified interface does not exist or the user is not privileged and tried to alter an interface's configuration.
SEE ALSO
esh(4), ifconfig(8)
HISTORY
The eshconfig command first appeared in NetBSD 1.4.
BSD
June 17, 2005 BSD