jOOQ doesn't implement indexing. I really suggest learning about those
first. You'll see immediately why jOOQ can't offer help with indexing your
data here (other than creating the CREATE INDEX statements, of course, but
it doesn't matter if you create them via jOOQ or directly in SQL).
If you're
Thanks Lukas, I'll take closer look at it. I know about it but not familiar
with implementing it.
I meant is there an implementation of indexing in jooq or just study about
it on our cloud servers? If jooq then do you know where to find a resource
for it? As well as connection pools?
But no
Josh,
I mean indexes on your database columns. Do you have an index on relevant
columns of your table? If you don't know about indexing in SQL, I highly
recommend this book (use the "jooq" discount code for 10% off, though it's
only 10 EUR for the PDF version):
Edit:
Running explain analyze on this query was 900ms :(
On Monday, February 26, 2024 at 1:25:46 PM UTC+8 Joshua Villano wrote:
Thank you for your response Lukas.
Firstly, the ms was a guess as i didnt run an analyze on the manual query,
but youre right it only runs on about 10ms.
Secondly,
Also, is connection pools just added as prop if we use hikari? What are the
ways to know what the correct sizing would be?
Thanks!
Josh
public DataSource dataSource() {
HikariConfig config = new HikariConfig();
config.addDataSourceProperty("cachePrepStmts", "true");
Thank you for your response Lukas.
Firstly, the ms was a guess as i didnt run an analyze on the manual query,
but youre right it only runs on about 10ms.
Secondly, we use JooqRecords and use Relations between jooq pojos, not sure
if that matters.
We also quite use the date manipulation
Hi Josh,
I'm not aware of any such significant performance penalties within jOOQ
itself (although, in case you're using R2DBC, there may still be issues
that I'm unaware of). There is also little risk of running into a
concurrency issue within jOOQ. The only place I recall where there's some
sort
Hi all,
First let me excuse myself if this is not the correct place to ask this,
and can you kindly point me in the right direction if ever, thanks!
Recently we've been noticing degrading performance whenever we use .select
on a single table in about 8-10 times concurrently. These range from
