yinyanlong / iosig

A tool that collects and analyzes I/O traces. It supports C and Fortran, with Java support in progress. It traces POSIX and MPI-IO in MPICH2.

IOSIG software is a toolkit developed by Scalable Computing Software Lab at Illinois Institute of Technology. In our research work, we designed and developed several performance optimization techniques for parallel I/O systems. Many of the techniques is application-aware that can utilize the I/O characteristics information of the applications to improve the efficiency of I/O system . We use IOSIG to collect and analyze applications I/O characteristics, which works as follows:

1. IOSIG trace collector records the trace of all the I/O operations of the application.
2. The IOSIG trace analyzer analyzes the trace files and recognizes the data access patterns.
3. The analysis results can be displayed using the browser-based dashboard.

See INSTALL.md for how to install and use the software. For more examples on how to use IOSIG to profile parallel I/O benchmarks and applications, check the GitHub project: https://github.com/yinyanlong/profiling_parallel_io.

Contact:

• Yanlong Yin ([email protected])
• Shuibing He ([email protected])
• Xian-He Sun ([email protected])

iosig's Issues

the calculation on nv_time seems wrong, because of some results are negative values

calculation of p-adj values

Hello Dear Yanlong Yin,

I recently came across your work on IOSig, and I must commend you on the excellent job. Your contributions are truly remarkable.

I have a specific question regarding the calculation of p-adj values in the context of box-plots. We plan to incorporate IOSig into our upcoming research paper and add supplementary figures. I would greatly appreciate it if you could provide some clarification on how the p-adj values in box-plots were computed in IOSig.

Thank you in advance for your time and assistance. I look forward to your guidance on this matter.

The MPI_File_seek's info is inconsistent with lseek

Lseek's info is right.

TODO: 'return 0' and 'exit(0)' are different. Exe_trace can handle the former but cannot handle the latter.

When use 'exit(0)', the program exit immediately and __cyg_profile_func_exit() will not be called.

access hole figures may not be generated

Check webapp.py for more details.

Code on access holes are commented out.

Fortran problem. Runs well. But runs differently with/without IOSIG.

posix and exe traces are put into IOSIG_DATA. mpiio traces are not.

one application may generate more than one trace directory in IOSIG_DATA

Such as the following case:

drwx------ 2 yanlong yanlong 4096 2014-02-08 19:26 yanlong_1386952277_mProjectPP
drwx------ 2 yanlong yanlong 4096 2014-02-08 19:26 yanlong_1386952277_mProjExecMPI
drwx------ 2 yanlong yanlong 4096 2014-02-08 19:26 yanlong_1386952282_mProjectPP
drwx------ 2 yanlong yanlong 4096 2014-02-08 19:26 yanlong_1386952283_mProjectPP
drwx------ 2 yanlong yanlong 4096 2014-02-08 19:26 yanlong_1386952297_mProjectPP

mProjExecMPI generated 5 directories.

Segmentation fault while running IOR with IOSIG