Bootchart - Boot Process Performance Visualization


 
Thread Tools Search this Thread
Operating Systems Solaris Solaris BigAdmin RSS Bootchart - Boot Process Performance Visualization
# 1  
Old 05-11-2009
Bootchart - Boot Process Performance Visualization

Bootchart is a tool for performance analysis and visualization of the GNU/Linux boot process. Resource utilization and process information are collected during the boot process and are later rendered in a PNG, SVG or EPS encoded chart.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

6 More Discussions You Might Find Interesting

1. Programming

Data Visualization For DNS, RADIUS Performance Logs

Hi there, I have a script running on some DNS servers to calculate TPS, Success Rate and other Performance Counters. My challenge is to get a Linux Data Visualization Software to collect these performance logs and produce a visualization that will be appealing to Business peeps. A sample of... (2 Replies)
Discussion started by: infinitydon
2 Replies

2. Red Hat

Boot process hang

Hello, Sometime i see that the boot process hangs. I am using rhel 6.2. At that time in the console i see Probing EDD (edd=off to disable)... SSH service seems to be started but i can't login... ssh logs (last lines) in verbose mode level 3: debug2: we did not send a packet,... (3 Replies)
Discussion started by: @dagio
3 Replies

3. Red Hat

Linux Boot Process

Explain Linux Boot Process??? (1 Reply)
Discussion started by: tejaschache
1 Replies

4. UNIX for Advanced & Expert Users

Trace Process performance Using PID

Hi, i want to track a process using its PID in SOLARIS. i have a code in C++ , which memory is increasing steeply increasing every 20 days, from the code i couldn't see any memory leak. is there any way in UNIX where with the help of PID i can trace the Process usage evry hour. ... (3 Replies)
Discussion started by: senkerth
3 Replies

5. UNIX for Dummies Questions & Answers

Checking Unix Performance - Why is a process running slowly?

Hi Please can someone explain to me how they would go about monitoring the performance of a process in Unix. Lets say that a user is running a process in Unix but it seems to be taking a long time, whereas it completed a lot quicker yesterday. How would you go about investigating what is causing... (1 Reply)
Discussion started by: Sunny Sid
1 Replies

6. UNIX for Advanced & Expert Users

MALLOC_MEM_ALLOC during boot process

I have COMPAQ DS 20 SERVER, During The Boot Process, There is an ERROR MESSAGE : malloc_mem_alloc : no space in map. AND the system can't boot , And i can't do anything. The server display : malloc_mem_alloc and the unique thing i can di is to restart the server with i/o buttom. HELP ME... (1 Reply)
Discussion started by: kamel267
1 Replies
Login or Register to Ask a Question
SYSTEMD-READAHEAD-REPLAY.SERVICE(8)			 systemd-readahead-replay.service		       SYSTEMD-READAHEAD-REPLAY.SERVICE(8)

NAME
systemd-readahead-replay.service, systemd-readahead-collect.service, systemd-readahead-done.service, systemd-readahead-done.timer, systemd- readahead - Disk read ahead logic SYNOPSIS
systemd-readahead-replay.service systemd-readahead-collect.service systemd-readahead-done.service systemd-readahead-done.timer /usr/lib/systemd/systemd-readahead/systemd-readahead [OPTIONS...] COMMAND [DIRECTORY | FILE] DESCRIPTION
systemd-readahead-collect.service is a service that collects disk usage patterns at boot time. systemd-readahead-replay.service is a service that replays this access data collected at the subsequent boot. Since disks tend to be magnitudes slower than RAM, this is intended to improve boot speeds by pre-loading early at boot all data on disk that is known to be read for the complete boot process. systemd-readahead-done.service is executed a short while after boot completed and signals systemd-readahead-collect.service to end data collection. On this signal, this service will then sort the collected disk accesses and store information about them in /.readahead. Normally, both systemd-readahead-collect.service and systemd-readahead-replay.service are activated at boot so that access patterns from the preceding boot are replayed and new data collected for the subsequent boot. However, on read-only media where the collected data cannot be stored, it might be a good idea to disable systemd-readahead-collect.service. On rotating media, when replaying disk accesses at early boot, systemd-readahead-replay.service will order read requests by their location on disk. On non-rotating media, they will be ordered by their original access timestamp. If the file system supports it, systemd-readahead-collect.service will also defragment and rearrange files on disk to optimize subsequent boot times. OPTIONS
systemd-readahead understands the following options: -h, --help Prints a short help text and exits. --max-files= Maximum number of files to read ahead. Only valid for thes collect command. --file-size-max= Maximum size of files in bytes to read ahead. Only valid for the collect and replay commands. --timeout= Maximum time in microseconds to spend collecting data. Only valid for the collect command. COMMANDS
The following commands are understood by systemd-readahead: collect [DIRECTORY] Collect read-ahead data on early boot. When terminating, it will write out a pack file to the indicated directory containing the read-ahead data. replay [DIRECTORY] Perform read-ahead on the specified directory tree. analyze [FILE] Dumps the content of the read-ahead pack file to the terminal. For each file, the output lists approximately how much will be read ahead by the replay command. SEE ALSO
systemd(1) systemd 208 SYSTEMD-READAHEAD-REPLAY.SERVICE(8)