Command Line Flags
Use these flags to have Skyline print out its version.
Use these flags to have Skyline print out information about its command line usage.
Shared Optional Arguments
The following command line arguments can be used with all of Skyline's subcommands.
Use this argument if you would like Skyline to write its logs to a separate file.
Set this command line flag to have Skyline print out more verbose logs. This is useful primarily for debugging.
skyline interactive path/to/entry_point.py
To launch an interactive profiling session, you will need to use the
interactive command. You need to specify the relative path to your project's
entry point file. This command will launch the Skyline profiling daemon and
will start Atom for you automatically.
skyline interactive you need to navigate to your project's
Set this command line flag
--host=<host name> and
Use these arguments to have the Skyline daemon bind to a custom host name and/or listen on a custom port. By default Skyline will bind to all network interfaces and will listen on port 60120.
Usually you do not need to set a custom host name nor port. These arguments are useful if you need to run multiple Skyline daemon processes, or if, due to a firewall, you need to have Skyline listen on a different port.
skyline memory --output results.sqlite path/to/entry_point.py
memory subcommand to get a memory usage report.
This allows you to get memory usage information without having to launch
Skyline's interactive profiler (i.e. the Skyline Atom plugin).
You need to specify the file where Skyline should save the memory report. This output file will be a SQLite database.
Run Time Profiling
skyline time --output results.sqlite path/to/entry_point.py
time subcommand to get a iteration run time
report. This allows you to get run time information
without having to launch Skyline's interactive profiler (i.e. the Skyline Atom
You need to specify the file where Skyline should save the run time report. This output file will be a SQLite database.