We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
table_column_details
At least I think it does. I tried running py-spy top -p $PID against a Datasette process that was trying to do:
py-spy top -p $PID
datasette covid.db --get '/covid/ny_times_us_counties.csv?_size=10&_stream=on'
While investigating:
And spotted this:
datasette covid.db --get /covid/ny_times_us_counties.csv?_size=10&_stream=on' (python v3.10.2) Total Samples 5800 GIL: 71.00%, Active: 98.00%, Threads: 4 %Own %Total OwnTime TotalTime Function (filename:line) 8.00% 8.00% 4.32s 4.38s sql_operation_in_thread (datasette/database.py:212) 5.00% 5.00% 3.77s 3.93s table_column_details (datasette/utils/__init__.py:614) 6.00% 6.00% 3.72s 3.72s _worker (concurrent/futures/thread.py:81) 7.00% 7.00% 2.98s 2.98s _read_from_self (asyncio/selector_events.py:120) 5.00% 6.00% 2.35s 2.49s detect_fts (datasette/utils/__init__.py:571) 4.00% 4.00% 1.34s 1.34s _write_to_self (asyncio/selector_events.py:140)
Relevant code:
datasette/datasette/utils/__init__.py
Lines 609 to 625 in 798f075
The text was updated successfully, but these errors were encountered:
Maybe it's because supports_table_xinfo() creates a brand new in-memory SQLite connection every time you call it?
supports_table_xinfo()
datasette/datasette/utils/sqlite.py
Lines 22 to 35 in 798f075
Actually no, I'm caching that already:
Lines 12 to 19 in 798f075
Sorry, something went wrong.
No branches or pull requests
At least I think it does. I tried running
py-spy top -p $PID
against a Datasette process that was trying to do:While investigating:
And spotted this:
Relevant code:
datasette/datasette/utils/__init__.py
Lines 609 to 625 in 798f075
The text was updated successfully, but these errors were encountered: