# YSQL vs YCQL performance

**URL:** <https://forum.yugabyte.com/t/ysql-vs-ycql-performance/521>\
**Category:** General\
**Created:** [October 3, 2019, 7:05pm UTC](https://forum.yugabyte.com/t/ysql-vs-ycql-performance/521 "2019-10-03T19:05:15Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nico](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.yugabyte.com/nico/32/166_2.png) [@Nico](https://forum.yugabyte.com/u/Nico)\
**Post date:** [October 3, 2019, 7:05pm UTC](https://forum.yugabyte.com/t/ysql-vs-ycql-performance/521/1 "2019-10-03T19:05:15Z")

</div>

Hello all,

Does YSQL have performance and scaling capabilities equivalent to YCQL?

Thanks

---

<div class="post-metadata">

**Author:** ![dorian\_yugabyte](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.yugabyte.com/dorian_yugabyte/32/206_2.png) [@dorian\_yugabyte](https://forum.yugabyte.com/u/dorian_yugabyte)\
**Post date:** [October 4, 2019, 10:28am UTC](https://forum.yugabyte.com/t/ysql-vs-ycql-performance/521/2 "2019-10-04T10:28:26Z")

</div>

Hi Nico,

It uses the same architecture underneath. Currently YCQL is more efficient since it’s been stable for quite some time but YSQL is getting there and will be on par and better in complex query scenarios.

Can you explain the app that you’re building and I’ll be able to help.

Regards,  
Dorian

---

<div class="post-metadata">

**Author:** ![kannan](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.yugabyte.com/kannan/32/18_2.png) [@kannan](https://forum.yugabyte.com/u/kannan)\
**Post date:** [October 4, 2019, 2:57pm UTC](https://forum.yugabyte.com/t/ysql-vs-ycql-performance/521/3 "2019-10-04T14:57:22Z")

</div>

Hi Nico,

To add to the previous reply:

You might also be interested [in this blog](https://blog.yugabyte.com/comparing-distributed-sql-performance-yugabyte-db-vs-amazon-aurora-postgresql-vs-cockroachdb/). It shows some performance numbers for YSQL & YSQL, and also scaling the YSQL workload to 1M writes/sec (compared to say Amazon Aurora which is not a horizontally scalable SQL system).

---

<div class="post-metadata">

**Author:** ![Nico](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.yugabyte.com/nico/32/166_2.png) [@Nico](https://forum.yugabyte.com/u/Nico)\
**Post date:** [October 5, 2019, 6:27pm UTC](https://forum.yugabyte.com/t/ysql-vs-ycql-performance/521/4 "2019-10-05T18:27:29Z")

</div>

Hi,

Thanks to you 2.

@dorian_yugabyte

> Can you explain the app that you’re building and I’ll be able to help.

I intend to use YugabyteDB for resources (normal CRUD: users, articles, etc).  
Where the charge is very high it’s for the chat, all messages are stored and there is a presence system.  
The operation of the presence system is: insert if not exists or update the user presence entry the user when the user join the chat, delete when the user leave the chat. Also, when the room where is the user is stored (so one update for each room change).

@kannan : The results are excellent and reassuring.

I deduce that YSQL will be good for everything, as a precaution YCQL for the presence system and the storage of messages.

Does this seem relevant to you?

Thanks

---

<div class="post-metadata">

**Author:** ![kannan](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.yugabyte.com/kannan/32/18_2.png) [@kannan](https://forum.yugabyte.com/u/kannan)\
**Post date:** [October 6, 2019, 3:10pm UTC](https://forum.yugabyte.com/t/ysql-vs-ycql-performance/521/5 "2019-10-06T15:10:30Z")

</div>

Hi Nico,

That sound quite reasonable and completely aligned with the kind of use cases we built YugabyteDB for.

Let us know if you have any additional issues/questions on schema/data model or YCQL vs. YSQL.

regards,  
Kannan

---

<div class="post-metadata">

**Author:** ![Nico](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.yugabyte.com/nico/32/166_2.png) [@Nico](https://forum.yugabyte.com/u/Nico)\
**Post date:** [December 10, 2019, 5:37pm UTC](https://forum.yugabyte.com/t/ysql-vs-ycql-performance/521/6 "2019-12-10T17:37:59Z")

</div>

I will.  
Thank you Kannan
