Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/jazzband/django-silk
Silky smooth profiling for Django
https://github.com/jazzband/django-silk
Last synced: 6 days ago
JSON representation
Silky smooth profiling for Django
- Host: GitHub
- URL: https://github.com/jazzband/django-silk
- Owner: jazzband
- License: mit
- Created: 2014-05-21T21:14:45.000Z (over 10 years ago)
- Default Branch: master
- Last Pushed: 2024-07-29T17:47:06.000Z (3 months ago)
- Last Synced: 2024-08-05T10:07:33.367Z (3 months ago)
- Language: Python
- Homepage:
- Size: 6.99 MB
- Stars: 4,353
- Watchers: 50
- Forks: 332
- Open Issues: 131
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
Awesome Lists containing this project
- -awesome-django - django-silk - Live profiling and inspection of HTTP requests and database queries. (Third-Party Packages / Performance)
- awesome-django-performance - Django Silk - Silk is a live profiling and inspection tool for the Django framework. Silk intercepts and stores HTTP requests and database queries before presenting them in a user interface for further inspection. (Profiling / Tools)
- awesome-django - django-silk - Silky smooth profiling for Django. (Debugging)
- awesome-django - django-silk - Live profiling and inspection of HTTP requests and database queries. (Third-Party Packages / Performance)
- starred-awesome - django-silk - Silky smooth profiling for Django (Python)
- best-of-web-python - GitHub - 35% open · ⏱️ 11.03.2024): (Web Testing)
- best-django-resource - django-silk - Live profiling, SQL query analysis, and HTTP request profiling for Django. (Performance)
README
# Silk
[](https://github.com/jazzband/django-silk/actions)
[](https://codecov.io/gh/jazzband/django-silk)
[](https://pypi.python.org/pypi/django-silk)
[](https://pypi.python.org/pypi/django-silk)
[](https://pypi.python.org/pypi/django-silk)
[](https://jazzband.co/)
Silk is a live profiling and inspection tool for the Django framework. Silk intercepts and stores HTTP requests and database queries before presenting them in a user interface for further inspection:
## Contents
* [Requirements](#requirements)
* [Installation](#installation)
* [Features](#features)
* [Configuration](#configuration)
* [Authentication/Authorisation](#authenticationauthorisation)
* [Request/Response bodies](#requestresponse-bodies)
* [Meta-Profiling](#meta-profiling)
* [Recording a fraction of requests](#recording-a-fraction-of-requests)
* [Limiting request/response data](#limiting-requestresponse-data)
* [Clearing logged data](#clearing-logged-data)
* [Contributing](#contributing)
* [Development Environment](#development-environment)
## Requirements
Silk has been tested with:
* Django: 4.2, 5.0, 5.1
* Python: 3.9, 3.10, 3.11, 3.12, 3.13
## Installation
Via pip into a `virtualenv`:
```bash
pip install django-silk
```
In `settings.py` add the following:
```python
MIDDLEWARE = [
...
'silk.middleware.SilkyMiddleware',
...
]
INSTALLED_APPS = (
...
'silk'
)
```
**Note:** The middleware placement is sensitive. If the middleware before `silk.middleware.SilkyMiddleware` returns from `process_request` then `SilkyMiddleware` will never get the chance to execute. Therefore you must ensure that any middleware placed before never returns anything from `process_request`. See the [django docs](https://docs.djangoproject.com/en/dev/topics/http/middleware/#process-request) for more information on this.
**Note:** If you are using `django.middleware.gzip.GZipMiddleware`, place that **before** `silk.middleware.SilkyMiddleware`, otherwise you will get an encoding error.
If you want to use custom middleware, for example you developed the subclass of `silk.middleware.SilkyMiddleware`, so you can use this combination of settings:
```python
# Specify the path where is the custom middleware placed
SILKY_MIDDLEWARE_CLASS = 'path.to.your.middleware.MyCustomSilkyMiddleware'
# Use this variable in list of middleware
MIDDLEWARE = [
...
SILKY_MIDDLEWARE_CLASS,
...
]
```
To enable access to the user interface add the following to your `urls.py`:
```python
urlpatterns += [path('silk/', include('silk.urls', namespace='silk'))]
```
before running migrate:
```bash
python manage.py migrate
python manage.py collectstatic
```
Silk will automatically begin interception of requests and you can proceed to add profiling
if required. The UI can be reached at `/silk/`
### Alternative Installation
Via [github tags](https://github.com/jazzband/django-silk/releases):
```bash
pip install https://github.com/jazzband/silk/archive/.tar.gz
```
You can install from master using the following, but please be aware that the version in master
may not be working for all versions specified in [requirements](#requirements)
```bash
pip install -e git+https://github.com/jazzband/django-silk.git#egg=django-silk
```
## Features
Silk primarily consists of:
* Middleware for intercepting Requests/Responses
* A wrapper around SQL execution for profiling of database queries
* A context manager/decorator for profiling blocks of code and functions either manually or dynamically.
* A user interface for inspection and visualisation of the above.
### Request Inspection
The Silk middleware intercepts and stores requests and responses in the configured database.
These requests can then be filtered and inspecting using Silk's UI through the request overview:
It records things like:
* Time taken
* Num. queries
* Time spent on queries
* Request/Response headers
* Request/Response bodies
and so on.
Further details on each request are also available by clicking the relevant request:
### SQL Inspection
Silk also intercepts SQL queries that are generated by each request. We can get a summary on things like
the tables involved, number of joins and execution time (the table can be sorted by clicking on a column header):
Before diving into the stack trace to figure out where this request is coming from:
### Profiling
Turn on the SILKY_PYTHON_PROFILER setting to use Python's built-in `cProfile` profiler. Each request will be separately profiled and the profiler's output will be available on the request's Profiling page in the Silk UI. Note that as of Python 3.12, `cProfile` cannot run concurrently so [django-silk under Python 3.12 and later will not profile if another profile is running](https://github.com/jazzband/django-silk/pull/692) (even its own profiler in another thread).
```python
SILKY_PYTHON_PROFILER = True
```
If you would like to also generate a binary `.prof` file set the following:
```python
SILKY_PYTHON_PROFILER_BINARY = True
```
When enabled, a graph visualisation generated using [gprof2dot](https://github.com/jrfonseca/gprof2dot) and [viz.js](https://github.com/almende/vis) is shown in the profile detail page:
A custom storage class can be used for the saved generated binary `.prof` files:
```python
# For Django >= 4.2 and Django-Silk >= 5.1.0:
# See https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-STORAGES
STORAGES = {
'SILKY_STORAGE': {
'BACKEND': 'path.to.StorageClass',
},
# ...
}
# For Django < 4.2 or Django-Silk < 5.1.0
SILKY_STORAGE_CLASS = 'path.to.StorageClass'
```
The default storage class is `silk.storage.ProfilerResultStorage`, and when using that you can specify a path of your choosing. You must ensure the specified directory exists.
```python
# If this is not set, MEDIA_ROOT will be used.
SILKY_PYTHON_PROFILER_RESULT_PATH = '/path/to/profiles/'
```
A download button will become available with a binary `.prof` file for every request. This file can be used for further analysis using [snakeviz](https://github.com/jiffyclub/snakeviz) or other cProfile tools
To retrieve which endpoint generates a specific profile file it is possible to add a stub of the request path in the file name with the following:
```python
SILKY_PYTHON_PROFILER_EXTENDED_FILE_NAME = True
```
Silk can also be used to profile specific blocks of code/functions. It provides a decorator and a context
manager for this purpose.
For example:
```python
from silk.profiling.profiler import silk_profile
@silk_profile(name='View Blog Post')
def post(request, post_id):
p = Post.objects.get(pk=post_id)
return render(request, 'post.html', {
'post': p
})
```
Whenever a blog post is viewed we get an entry within the Silk UI:
Silk profiling not only provides execution time, but also collects SQL queries executed within the block in the same fashion as with requests:
#### Decorator
The silk decorator can be applied to both functions and methods
```python
from silk.profiling.profiler import silk_profile
# Profile a view function
@silk_profile(name='View Blog Post')
def post(request, post_id):
p = Post.objects.get(pk=post_id)
return render(request, 'post.html', {
'post': p
})
# Profile a method in a view class
class MyView(View):
@silk_profile(name='View Blog Post')
def get(self, request):
p = Post.objects.get(pk=post_id)
return render(request, 'post.html', {
'post': p
})
```
#### Context Manager
Using a context manager means we can add additional context to the name which can be useful for
narrowing down slowness to particular database records.
```python
def post(request, post_id):
with silk_profile(name='View Blog Post #%d' % self.pk):
p = Post.objects.get(pk=post_id)
return render(request, 'post.html', {
'post': p
})
```
#### Dynamic Profiling
One of Silk's more interesting features is dynamic profiling. If for example we wanted to profile a function in a dependency to which we only have read-only access (e.g. system python libraries owned by root) we can add the following to `settings.py` to apply a decorator at runtime:
```python
SILKY_DYNAMIC_PROFILING = [{
'module': 'path.to.module',
'function': 'MyClass.bar'
}]
```
which is roughly equivalent to:
```python
class MyClass:
@silk_profile()
def bar(self):
pass
```
The below summarizes the possibilities:
```python
"""
Dynamic function decorator
"""
SILKY_DYNAMIC_PROFILING = [{
'module': 'path.to.module',
'function': 'foo'
}]
# ... is roughly equivalent to
@silk_profile()
def foo():
pass
"""
Dynamic method decorator
"""
SILKY_DYNAMIC_PROFILING = [{
'module': 'path.to.module',
'function': 'MyClass.bar'
}]
# ... is roughly equivalent to
class MyClass:
@silk_profile()
def bar(self):
pass
"""
Dynamic code block profiling
"""
SILKY_DYNAMIC_PROFILING = [{
'module': 'path.to.module',
'function': 'foo',
# Line numbers are relative to the function as opposed to the file in which it resides
'start_line': 1,
'end_line': 2,
'name': 'Slow Foo'
}]
# ... is roughly equivalent to
def foo():
with silk_profile(name='Slow Foo'):
print (1)
print (2)
print(3)
print(4)
```
Note that dynamic profiling behaves in a similar fashion to that of the python mock framework in that
we modify the function in-place e.g:
```python
""" my.module """
from another.module import foo
# ...do some stuff
foo()
# ...do some other stuff
```
,we would profile `foo` by dynamically decorating `my.module.foo` as opposed to `another.module.foo`:
```python
SILKY_DYNAMIC_PROFILING = [{
'module': 'my.module',
'function': 'foo'
}]
```
If we were to apply the dynamic profile to the functions source module `another.module.foo` **after**
it has already been imported, no profiling would be triggered.
#### Custom Logic for Profiling
Sometimes you may want to dynamically control when the profiler runs. You can write your own logic for when to enable the profiler. To do this add the following to your `settings.py`:
This setting is mutually exclusive with SILKY_PYTHON_PROFILER and will be used over it if present. It will work with SILKY_DYNAMIC_PROFILING.
```python
def my_custom_logic(request):
return 'profile_requests' in request.session
SILKY_PYTHON_PROFILER_FUNC = my_custom_logic # profile only session has recording enabled.
```
You can also use a `lambda`.
```python
# profile only session has recording enabled.
SILKY_PYTHON_PROFILER_FUNC = lambda request: 'profile_requests' in request.session
```
### Code Generation
Silk currently generates two bits of code per request:
Both are intended for use in replaying the request. The curl command can be used to replay via command-line and the python code can be used within a Django unit test or simply as a standalone script.
## Configuration
### Authentication/Authorisation
By default anybody can access the Silk user interface by heading to `/silk/`. To enable your Django
auth backend place the following in `settings.py`:
```python
SILKY_AUTHENTICATION = True # User must login
SILKY_AUTHORISATION = True # User must have permissions
```
If `SILKY_AUTHORISATION` is `True`, by default Silk will only authorise users with `is_staff` attribute set to `True`.
You can customise this using the following in `settings.py`:
```python
def my_custom_perms(user):
return user.is_allowed_to_use_silk
SILKY_PERMISSIONS = my_custom_perms
```
You can also use a `lambda`.
```python
SILKY_PERMISSIONS = lambda user: user.is_superuser
```
### Request/Response bodies
By default, Silk will save down the request and response bodies for each request for future viewing
no matter how large. If Silk is used in production under heavy volume with large bodies this can have
a huge impact on space/time performance. This behaviour can be configured with the following options:
```python
SILKY_MAX_REQUEST_BODY_SIZE = -1 # Silk takes anything <0 as no limit
SILKY_MAX_RESPONSE_BODY_SIZE = 1024 # If response body>1024 bytes, ignore
```
### Meta-Profiling
Sometimes it is useful to be able to see what effect Silk is having on the request/response time. To do this add
the following to your `settings.py`:
```python
SILKY_META = True
```
Silk will then record how long it takes to save everything down to the database at the end of each
request:
Note that in the above screenshot, this means that the request took 29ms (22ms from Django and 7ms from Silk)
### Recording a Fraction of Requests
On high-load sites it may be helpful to only record a fraction of the requests that are made. To do this add the following to your `settings.py`:
Note: This setting is mutually exclusive with SILKY_INTERCEPT_FUNC.
```python
SILKY_INTERCEPT_PERCENT = 50 # log only 50% of requests
```
#### Custom Logic for Recording Requests
On high-load sites it may also be helpful to write your own logic for when to intercept requests. To do this add the following to your `settings.py`:
Note: This setting is mutually exclusive with SILKY_INTERCEPT_PERCENT.
```python
def my_custom_logic(request):
return 'record_requests' in request.session
SILKY_INTERCEPT_FUNC = my_custom_logic # log only session has recording enabled.
```
You can also use a `lambda`.
```python
# log only session has recording enabled.
SILKY_INTERCEPT_FUNC = lambda request: 'record_requests' in request.session
```
### Limiting request/response data
To make sure silky garbage collects old request/response data, a config var can be set to limit the number of request/response rows it stores.
```python
SILKY_MAX_RECORDED_REQUESTS = 10**4
```
The garbage collection is only run on a percentage of requests to reduce overhead. It can be adjusted with this config:
```python
SILKY_MAX_RECORDED_REQUESTS_CHECK_PERCENT = 10
```
In case you want decouple silk's garbage collection from your webserver's request processing, set SILKY_MAX_RECORDED_REQUESTS_CHECK_PERCENT=0 and trigger it manually, e.g. in a cron job:
```bash
python manage.py silk_request_garbage_collect
```
### Enable query analysis
To enable query analysis when supported by the dbms a config var can be set in order to execute queries with the analyze features.
```python
SILKY_ANALYZE_QUERIES = True
```
**Warning:** This setting may cause the database to execute the same query twice, depending on the backend. For instance, `EXPLAIN ANALYZE` in Postgres will [actually execute the query](https://www.postgresql.org/docs/current/sql-explain.html), which may result in unexpected data updates. Set this to True with caution.
To pass additional params for profiling when supported by the dbms (e.g. VERBOSE, FORMAT JSON), you can do this in the following manner.
```python
SILKY_EXPLAIN_FLAGS = {'format':'JSON', 'costs': True}
```
### Masking sensitive data on request body
By default, Silk is filtering values that contains the following keys (they are case insensitive)
```python
SILKY_SENSITIVE_KEYS = {'username', 'api', 'token', 'key', 'secret', 'password', 'signature'}
```
But sometimes, you might want to have your own sensitive keywords, then above configuration can be modified
```python
SILKY_SENSITIVE_KEYS = {'custom-password'}
```
### Clearing logged data
A management command will wipe out all logged data:
```bash
python manage.py silk_clear_request_log
```
## Contributing
[](https://jazzband.co/)
This is a [Jazzband](https://jazzband.co/) project. By contributing you agree to abide by the [Contributor Code of Conduct](https://jazzband.co/about/conduct) and follow the [guidelines](https://jazzband.co/about/guidelines).
### Development Environment
Silk features a project named `project` that can be used for `silk` development. It has the `silk` code symlinked so
you can work on the sample `project` and on the `silk` package at the same time.
In order to setup local development you should first install all the dependencies for the test `project`. From the
root of the `project` directory:
```bash
pip install -r requirements.txt
```
You will also need to install `silk`'s dependencies. From the root of the git repository:
```bash
pip install -e .
```
At this point your virtual environment should have everything it needs to run both the sample `project` and
`silk` successfully.
Before running, you must set the `DB_ENGINE` and `DB_NAME` environment variables:
```bash
export DB_ENGINE=sqlite3
export DB_NAME=db.sqlite3
```
For other combinations, check [`tox.ini`](./tox.ini).
Now from the root of the sample `project` apply the migrations
```bash
python manage.py migrate
```
Now from the root of the sample `project` directory start the django server
```bash
python manage.py runserver
```
#### Running the tests
```bash
cd project
python manage.py test
```
Happy profiling!