Click the Start Test button to connect this web application directly to the sample database and execute SQL queries for 20 seconds.
Performance
Step 1 – Direct
Average
Press "Start Test" Button
Step 2 – PolyScale
Average
Press "Start Test" Button
Performance Graph
Press "Start Test" Button
Application Log
Press "Start Test" Button
FAQ
TLDR: A live demo of PolyScale's database edge cache. Visit PolyScale.ai for full details.
PolyScale.ai is a database edge cache that lowers latency and accelerates query performance and concurrency.
This demo site first runs two latency tests: a direct app to db connection then an app to db via PolyScale connection. Test queries are executed for 20 seconds each and the results compared.
For simplicity, this application uses a single SQL query and varies the dept_name query parameter:
SELECTCOUNT(*)AS employ_count,MAX(salary)AS max_salary,MIN(salary)AS min_salary
FROM employees e
INNERJOIN dept_emp de ON e.emp_no = de.emp_no
INNERJOIN departments d ON de.dept_no = d.dept_no
INNERJOIN salaries s ON s.emp_no = e.emp_no
WHERE d.dept_name ='Sales'
Yes, the playground database is publicly accessible and can be connected to by any MySQL v8.0 compatible client. As per the demo, a direct connection can be made or a connection via PolyScale (cached reads). The direct to db credentials are as follows:
Hostname: database-1.ctiftbwzooit.eu-west-3.rds.amazonaws.com Port: 3306 DB User: polyscale DB Pass: playground
PolyScale.ai is a global database edge cache as a service. It solves:
Regional Latency - Make data-driven apps blisteringly fast, no matter where the audience resides.
Read Query Performance - Execute any database query in single digit milliseconds, while also reducing performance variability.
High Scalability & Availability - Scale to thousands of concurrent connections with multi-region failover.
Reduced DB Workloads & Costs - Decouple reads to free up resources for writes, reduce infrastructure costs.
The TTL of the demo query is set to 120 seconds. Note: this is a shared demo environment and hence the responses may already be cached, or invalidated 120 seconds after another user has started their queries. All other queries that can be initiated by connecting any MySQL client to PolyScale, are cached for 24 hours.