首页
学习
活动
专区
工具
TVP
发布
精选内容/技术社群/优惠产品,尽在小程序
立即前往
您找到你想要的搜索结果了吗?
是的
没有找到

fio基础11

rdma The RDMA I/O engine supports both RDMA memory semantics (RDMA_WRITE/RDMA_READ) and channel semantics (Send/Recv) for the InfiniBand, RoCE and iWARP protocols. falloc IO engine that does regular fallocate to simulate data transfer as fio ioengine. DDIR_READ does fallocate(,mode = keep_size,) DDIR_WRITE does fallocate(,mode = 0) DDIR_TRIM does fallocate(,mode = punch_hole) e4defrag IO engine that does regular EXT4_IOC_MOVE_EXT ioctls to simulate defragment activity in request to DDIR_WRITE event rbd IO engine supporting direct access to Ceph Rados Block Devices (RBD) via librbd without the need to use the kernel rbd driver. This ioengine defines engine specific options. gfapi Using Glusterfs libgfapi sync interface to direct access to Glusterfs volumes without options. gfapi_async Using Glusterfs libgfapi async interface to direct access to Glusterfs volumes without having to go through FUSE. This ioengine defines engine specific options. libhdfs Read and write through Hadoop (HDFS). The 'filename' option is used to specify host, port of the hdfs name-node to connect. This engine interprets offsets a little differently. In HDFS, files once created cannot be modified. So random writes are not possible. To imitate this, libhdfs engine expects bunch of small files to be created over HDFS, and engine will randomly pick a file out of those files based on the offset generated by fio backend. (see the example job file to create such files, use rw=write option). Please note, you might want to set necessary environment variables to work with hdfs/libhdfs properly. mtd Read, write and erase an MTD character device (e.g., /dev/mtd0). Discards are treated as erases. Depending on the underlying device type, the I/O may have to go in a certain pattern, e.g., on NAND, writing sequentially to erase blocks and discarding before overwriting. The w

04

fio基础10

bs_is_seq_randIfthisoptionisset,fiowillusethenormalread,writeblocksizesettingsassequential,randominstead.AnyrandomreadorwritewillusetheWRITEblocksizesettings,andanysequentialreadorwritewillusetheREADblocksizesetting.zero_buffersIfthisoptionisgiven,fiowillinittheIObufferstoallzeroes.Thedefaultistofillthemwithrandomdata.refill_buffersIfthisoptionisgiven,fiowillrefilltheIObuffersoneverysubmit.Thedefaultistoonlyfillitatinittimeandreusethatdata.Onlymakessenseifzero_buffersisn't specified, naturally. If data verification is enabled, refill_buffers is also automatically enabled. scramble_buffers=bool If refill_buffers is too costly and the target is using data deduplication, then setting this option will slightly modify the IO buffer contents to defeat normal de-dupe attempts. This is not enough to defeat more clever block compression attempts, but it will stop naive dedupe of blocks. Default: true. buffer_compress_percentage=int If this is set, then fio will attempt to provide IO buffer content (on WRITEs) that compress to the specified level. Fio does this by providing a mix of random data and a fixed pattern. The fixed pattern is either zeroes, or the pattern specified by buffer_pattern. If the pattern option is used, it might skew the compression ratio slightly. Note that this is per block size unit, for file/disk wide compression level that matches this setting, you'llalsowanttosetrefill_buffers.buffer_compress_chunk=intSeebuffer_compress_percentage.Thissettingallowsfiotomanagehowbigtherangesofrandomdataandzeroeddatais.Withoutthisset,fiowillprovidebuffer_compress_percentageofblocksizerandomdata,followedbytheremainingzeroed.Withthissettosomechunksizesmallerthantheblocksize,fiocanalternaterandomandzeroeddatathroughouttheIObuffer.buffer_pattern=strIfset,fiowillfilltheiobufferswiththispattern.Ifnotset,thecontentsofiobuffersisdefinedbytheotheroptionsrelatedtobuffercontents.Thesettingcanbeanypatternofbytes,andcanbeprefixedwith0xforhexvalues.Itmayalsobeastring,wherethestringmustthenbewrappedwit

04

SAP BASIS服务器参数大全

path: /usr/sap/PRD/SYS/profile profile: PRD_DVEBMGS00_sapapp 如果您想查看所有的参数及当前设定,可使用SA38 执行程序 RSPARAM 修改附加配置 T-CODE:RZ10 进行SAP系统参数的设置,设置后需激活参数并重启SAP实例,配置参数才会生效 login/system_client  登录时默认的Client号 login/password_expiration_time  密码有效期 login/fails_to_user_lock   密码输错多少次后锁定 login/failed_user_auto_unlock  用户失效后多长时间解锁 rdisp/mshost   状态栏中显示的系统名称 rdisp/rfc_use_quotas  是否激活配额资源分配,0是关闭,1是启用.以下相关限制必须这个为1时才生效. rdisp/gui_auto_logout 表示如果客户在指定时间内没有进行任何操作,则会自动退出SAP系统。时间为秒 rdisp/max_wprun_time   程序运行的最长时间限制 rdisp/rfc_max_login   最大SAP用户登录数 login/disable_multi_gui_login  限制用户多次登录,该参数可以设置同个client 同个用户ID可以允许同时登录几个,当设为1时,系统将提示用户选择: 'Terminate the Current Sessions' or 'Terminate this Login.' ,以达到保证只允许一个登录. rdisp/tm_max_no   这个参数是限制每个实例最大的用户数,默认是200个. rdisp/rfc_max_own_login   一个程序在一个服务器 上允许分配的RFC资源个数,也就是同时能运行多少个.默认值25. rdisp/rfc_min_wait_dia_wp 设置RFC保留的会话设置, rdisp/wp_no_dia   在一个实例中处理的会话数目,如果设置为10,rdisp/rfc_min_wait_dia_wp=3  则可用的会话处理是7,3个被保留 rdisp/rfc_max_own_used_wp rdisp/rfc_max_comm_entries rdisp/rfc_max_wait_time rdisp/btctime SAP调度器(SAYMSSY2),定期自动运行,由这个参数指定运行时间间隔。 rdisp/btcname 事件触发后运行envent scheduler 主机名称 rspo/store_location 文件存储位置(假脱机) wdisp/server_info_location   the default is /msgserver/text/logon.The URL to retrieve the list   is determined this parameter rdisp/mshost  信息服务器设置 ms/http_port  http服务端口 auth/new_buffering to  该参数设为4,权限的修改将立即起作用,不用用户重新登录. Note 209899. 系统性能参数调整类: SAP 描述文件参数 参数   建议值 abap/use_paging    建议值:0(关闭)使用:重新激活旧的 ABAP/4 分页系统获得清单和简单表格类型。 abap/heaplimit    建议值:20000000(20MB)使用:用户环境完成处理后,重新启动一个工作进程来释放局部私有存储。 abap/heap_area_total    建议值:500000000(500MB)使用:设置 SAP 应用程序服务器可以使用的进程局部存储限制。对服务器的使用或交换空间设置限制。 em/initial_size_MB    建议值:250(250 MB,每个用户五 MB)使用:SAP 共享内存的大小。 em/stat_log_size_Mb    建议值:20使用:统计。 em/stat_log_size_timeout    建议值:600使用:统计。 rdisp/ROLL_MAXFS    建议值:32768使用:滚动文件的最大规模。 rdisp/ROLL_SHM    建议值:4096 使用:滚动缓冲区大小。 rdisp/PG_MAXFS    建议值:32768使用:ABAP/4 分页文件的最大规模。 rdisp/PG_SHM    建议值:0使用:分页缓冲区大小。 ztta/roll_area:滚动区域    建议值:1000000 (1 million bytes)使用:滚动区域大小。 T-CODE

01
领券