2021.01.15 08:26:11.003616 [uid:0,gid:0,pid:4403] write (17666,390,951582): OK <0.000006>
```
The last number on each line is the time (in seconds) current operation takes. You can use this to debug and analyze performance issues. We will provide more tools to analyze it.
The last number on each line is the time (in seconds) current operation takes. You can use this directly to debug and analyze performance issues, or try `./juicefs profile /jfs` to monitor real time statistics. Please run `./juicefs profile -h` or refer to [here](docs/en/operations_profiling.md) to learn more about this subcommand.
2021.01.15 08:26:11.003616 [uid:0,gid:0,pid:4403] write (17666,390,951582): OK <0.000006>
```
The last number on each line is the time (in seconds) current operation takes. You can use this to debug and analyze performance issues.
The last number on each line is the time (in seconds) current operation takes. You can use this to know information of every operation, or try `juicefs profile /jfs` to monitor aggregated statistics.
JuiceFS has a special virtual file named `.accesslog` to track every operation occurred within its client. This file may generate thousands of log entries per second when under pressure, making it hard to find out what is actually going on at a certain time. Thus, we made a simple tool called `juicefs profile` to show an overview of recently completed operations. The basic idea is to aggregate all logs in the past interval and display statistics periodically, like:
For now there are 2 modes of profiling: real time and replay.
### Real Time Mode
By executing the following command you can watch real time operations under the mount point:
```bash
$ juicefs profile MOUNTPOINT
```
The result is sorted in a descending order by number.
### Replay Mode
Running the profile command on an existing log file enables the **replay mode**:
```
$ juicefs profile LOGFILE
```
When debugging or analyzing perfomance issues, it is usually more practical to record access log first and then replay it(multiple times). For example:
```bash
$ cat /jfs/.accesslog > /tmp/jfs-oplog
# later
$ juicefs profile /tmp/jfs-oplog
```
The replay could be paused anytime by <kbd>enter/return</kbd>, and continues by pressing it again.
## Filter
Sometimes we are only interested in a certain user or process, then we can filter others out by specifying its IDs; e.g:
```bash
$ juicefs profile /tmp/jfs-oplog --uid 12345
```
For more information, please run `juicefs profile -h`.