Transactional database applications are extremely latency sensitive
for two reasons. First, in many transactional applications (e.g.,
database-backed websites), there is typically a hard response time
limit of a few hundred milliseconds, including the time to execute
application logic, retrieve query results, and generate HTML . Saving
even a few tens of milliseconds of latency per transaction can be
important in meeting these latency bounds. Second, longer-latency
transactions hold locks longer, which can severely limit maximum
system throughput in highly concurrent systems.
Stored procedures are a widely used technique for improving the
latency of database applications. The idea behind stored procedures
is to rewrite sequences of application logic that are interleaved with
database commands (e.g., SQL queries) into parameterized blocks
of code that are stored on the database server. The application
Transactional database applications are extremely latency sensitive
for two reasons. First, in many transactional applications (e.g.,
database-backed websites), there is typically a hard response time
limit of a few hundred milliseconds, including the time to execute
application logic, retrieve query results, and generate HTML . Saving
even a few tens of milliseconds of latency per transaction can be
important in meeting these latency bounds. Second, longer-latency
transactions hold locks longer, which can severely limit maximum
system throughput in highly concurrent systems.
Stored procedures are a widely used technique for improving the
latency of database applications. The idea behind stored procedures
is to rewrite sequences of application logic that are interleaved with
database commands (e.g., SQL queries) into parameterized blocks
of code that are stored on the database server. The application
การแปล กรุณารอสักครู่..
