Thanks to visit codestin.com
Credit goes to github.com

Skip to content
This repository was archived by the owner on Aug 2, 2023. It is now read-only.

Conversation

@achimnol
Copy link
Member

No description provided.

@achimnol achimnol added this to the 20.09 milestone Apr 20, 2021
@achimnol achimnol added the bug label Apr 20, 2021
@codecov
Copy link

codecov bot commented Apr 20, 2021

Codecov Report

Merging #421 (a933a8d) into main (35ddf26) will decrease coverage by 0.05%.
The diff coverage is 30.76%.

Impacted file tree graph

@@            Coverage Diff             @@
##             main     #421      +/-   ##
==========================================
- Coverage   48.90%   48.84%   -0.06%     
==========================================
  Files          52       52              
  Lines        8322     8332      +10     
==========================================
  Hits         4070     4070              
- Misses       4252     4262      +10     
Impacted Files Coverage Δ
src/ai/backend/manager/models/keypair.py 47.84% <16.66%> (-0.76%) ⬇️
src/ai/backend/manager/api/auth.py 51.16% <42.85%> (-0.90%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 35ddf26...a933a8d. Read the comment docs.

@achimnol achimnol merged commit cc6a37e into main May 7, 2021
@achimnol achimnol deleted the fix/remove-num_queries-counting branch May 7, 2021 04:39
achimnol added a commit that referenced this pull request May 10, 2021
* Now all DB transactions use the "SERIALIZABLE" isolation level with explicit retries.
* Now DB transactions that includes only SELECT queries are marked as "read-only" so that
  the PostgreSQL engine could optimize concurrent access with the new isolation level.
  All future codes should use `beegin_readonly()` method from our own subclassed SQLAlchemy
  engine instance replacing all existing `db` context variables.
* Remove excessive database updates due to keypair API query counts and kernel API query counts.
  The keypair API query count is re-written to use Redis with one month retention. (#421)
  Now just calling an API does not trigger updates in the PostgreSQL database.
* Fix unnecessary database updates for agent heartbeats.
* Split many update-only DB transactions into smaller units, such as resource recalculation.
* Use PostgreSQL advisory locks to make the scheduling decision process as a critical section.
* Fix some of variable binding issues with nested functions inside loops.
* Apply event message coalescing to prevent event bursts (e.g., `DoScheduleEvent` fired after
  enqueueing new session requests) which hurts the database performance and potentially
  break the transaction isolation guarantees.
achimnol added a commit that referenced this pull request May 10, 2021
* This is to avoid excessive write transaction overheads to the database.
* Set the retention time since last update to one month.

Backported-From: main
Backported-To: 21.03
achimnol added a commit that referenced this pull request May 10, 2021
* This is to avoid excessive write transaction overheads to the database.
* Set the retention time since last update to one month.

Backported-From: main
Backported-To: 20.09
achimnol added a commit that referenced this pull request May 10, 2021
* Now all DB transactions use the "SERIALIZABLE" isolation level with explicit retries.
* Now DB transactions that includes only SELECT queries are marked as "read-only" so that
  the PostgreSQL engine could optimize concurrent access with the new isolation level.
  All future codes should use `beegin_readonly()` method from our own subclassed SQLAlchemy
  engine instance replacing all existing `db` context variables.
* Remove excessive database updates due to keypair API query counts and kernel API query counts.
  The keypair API query count is re-written to use Redis with one month retention. (#421)
  Now just calling an API does not trigger updates in the PostgreSQL database.
* Fix unnecessary database updates for agent heartbeats.
* Split many update-only DB transactions into smaller units, such as resource recalculation.
* Use PostgreSQL advisory locks to make the scheduling decision process as a critical section.
* Fix some of variable binding issues with nested functions inside loops.
* Apply event message coalescing to prevent event bursts (e.g., `DoScheduleEvent` fired after
  enqueueing new session requests) which hurts the database performance and potentially
  break the transaction isolation guarantees.

Backported-From: main
Backported-To: 21.03
achimnol added a commit that referenced this pull request May 10, 2021
* Now all DB transactions use the "SERIALIZABLE" isolation level with explicit retries.
* Now DB transactions that includes only SELECT queries are marked as "read-only" so that
  the PostgreSQL engine could optimize concurrent access with the new isolation level.
  All future codes should use `beegin_readonly()` method from our own subclassed SQLAlchemy
  engine instance replacing all existing `db` context variables.
* Remove excessive database updates due to keypair API query counts and kernel API query counts.
  The keypair API query count is re-written to use Redis with one month retention. (#421)
  Now just calling an API does not trigger updates in the PostgreSQL database.
* Fix unnecessary database updates for agent heartbeats.
* Split many update-only DB transactions into smaller units, such as resource recalculation.
* Use PostgreSQL advisory locks to make the scheduling decision process as a critical section.
* Fix some of variable binding issues with nested functions inside loops.
* Apply event message coalescing to prevent event bursts (e.g., `DoScheduleEvent` fired after
  enqueueing new session requests) which hurts the database performance and potentially
  break the transaction isolation guarantees.

Backported-From: main
Backported-To: 20.09
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants