Play Scala Slick query incredibly slow on AWS RDS
I'm currently encountring a performance issue with play slick hitting a Postgresql database on AWS RDS. The app was running quite well 2 days ago but now some queries are freezing the app.
A join query with a result of only 8 rows would take up to 2300ms and one resulting with 30 row is taking more than 4000ms.
Here is the query performed as an example:
protected def jobOfferQuery = for {
(((mission, client), process), clientCompany) <- jobOffers
.joinLeft(users).on(_.clientId === _.userId)
.joinLeft(processes).on(_._1.offerId === _.jobOfferId)
.joinLeft(companies)
} yield (mission, client, process, clientCompany)
Here is my slick configuration for my play app:
database {
dataSourceClass = org.postgresql.ds.PGSimpleDataSource
properties = {
serverName = ${app.postgres.host}
portNumber = ${app.postgres.port}
databaseName = ${app.postgres.db}
user = ${app.postgres.user}
password = ${app.postgres.password}
}
poolName = ${app.postgres.poolName}
numThreads=5
driver="slick.driver.PostgresDriver$"
}
How can it be so slow ? Should I add more hikarycp configuration ?
Thank you so much for helping me out, much appreciated ..
postgresql scala playframework amazon-rds slick
asked Nov 15 '18 at 18:52
Mael RazavetMael Razavet
11210
add a comment |
I'm currently encountring a performance issue with play slick hitting a Postgresql database on AWS RDS. The app was running quite well 2 days ago but now some queries are freezing the app.
A join query with a result of only 8 rows would take up to 2300ms and one resulting with 30 row is taking more than 4000ms.
Here is the query performed as an example:
protected def jobOfferQuery = for {
(((mission, client), process), clientCompany) <- jobOffers
.joinLeft(users).on(_.clientId === _.userId)
.joinLeft(processes).on(_._1.offerId === _.jobOfferId)
.joinLeft(companies)
} yield (mission, client, process, clientCompany)
Here is my slick configuration for my play app:
database {
dataSourceClass = org.postgresql.ds.PGSimpleDataSource
properties = {
serverName = ${app.postgres.host}
portNumber = ${app.postgres.port}
databaseName = ${app.postgres.db}
user = ${app.postgres.user}
password = ${app.postgres.password}
}
poolName = ${app.postgres.poolName}
numThreads=5
driver="slick.driver.PostgresDriver$"
}
How can it be so slow ? Should I add more hikarycp configuration ?
Thank you so much for helping me out, much appreciated ..
postgresql scala playframework amazon-rds slick
asked Nov 15 '18 at 18:52
Mael RazavetMael Razavet
11210
Have you tried to check wich query slick is generates and than this query with explain command postgresql.org/docs/9.3/sql-explain.html?
– Valerii Rusakov
Nov 17 '18 at 18:24
1
Found the solution .. The third join was without a condition is simply killing the performance. It was an idiot mistake on my side.
– Mael Razavet
Nov 19 '18 at 16:25
add a comment |
I'm currently encountring a performance issue with play slick hitting a Postgresql database on AWS RDS. The app was running quite well 2 days ago but now some queries are freezing the app.
A join query with a result of only 8 rows would take up to 2300ms and one resulting with 30 row is taking more than 4000ms.
Here is the query performed as an example:
protected def jobOfferQuery = for {
(((mission, client), process), clientCompany) <- jobOffers
.joinLeft(users).on(_.clientId === _.userId)
.joinLeft(processes).on(_._1.offerId === _.jobOfferId)
.joinLeft(companies)
} yield (mission, client, process, clientCompany)
Here is my slick configuration for my play app:
database {
dataSourceClass = org.postgresql.ds.PGSimpleDataSource
properties = {
serverName = ${app.postgres.host}
portNumber = ${app.postgres.port}
databaseName = ${app.postgres.db}
user = ${app.postgres.user}
password = ${app.postgres.password}
}
poolName = ${app.postgres.poolName}
numThreads=5
driver="slick.driver.PostgresDriver$"
}
How can it be so slow ? Should I add more hikarycp configuration ?
Thank you so much for helping me out, much appreciated ..
postgresql scala playframework amazon-rds slick
asked Nov 15 '18 at 18:52
Mael RazavetMael Razavet
11210
I'm currently encountring a performance issue with play slick hitting a Postgresql database on AWS RDS. The app was running quite well 2 days ago but now some queries are freezing the app.
A join query with a result of only 8 rows would take up to 2300ms and one resulting with 30 row is taking more than 4000ms.
Here is the query performed as an example:
protected def jobOfferQuery = for {
(((mission, client), process), clientCompany) <- jobOffers
.joinLeft(users).on(_.clientId === _.userId)
.joinLeft(processes).on(_._1.offerId === _.jobOfferId)
.joinLeft(companies)
} yield (mission, client, process, clientCompany)
Here is my slick configuration for my play app:
database {
dataSourceClass = org.postgresql.ds.PGSimpleDataSource
properties = {
serverName = ${app.postgres.host}
portNumber = ${app.postgres.port}
databaseName = ${app.postgres.db}
user = ${app.postgres.user}
password = ${app.postgres.password}
}
poolName = ${app.postgres.poolName}
numThreads=5
driver="slick.driver.PostgresDriver$"
}
How can it be so slow ? Should I add more hikarycp configuration ?
Thank you so much for helping me out, much appreciated ..
postgresql scala playframework amazon-rds slick
postgresql scala playframework amazon-rds slick
asked Nov 15 '18 at 18:52
Mael RazavetMael Razavet
11210
asked Nov 15 '18 at 18:52
Mael RazavetMael Razavet
11210
asked Nov 15 '18 at 18:52
Mael RazavetMael Razavet
11210
asked Nov 15 '18 at 18:52
Mael RazavetMael Razavet
11210
asked Nov 15 '18 at 18:52
Mael RazavetMael Razavet
11210
11210
Have you tried to check wich query slick is generates and than this query with explain command postgresql.org/docs/9.3/sql-explain.html?
– Valerii Rusakov
Nov 17 '18 at 18:24
1
Found the solution .. The third join was without a condition is simply killing the performance. It was an idiot mistake on my side.
– Mael Razavet
Nov 19 '18 at 16:25
add a comment |
Have you tried to check wich query slick is generates and than this query with explain command postgresql.org/docs/9.3/sql-explain.html?
– Valerii Rusakov
Nov 17 '18 at 18:24
1
Found the solution .. The third join was without a condition is simply killing the performance. It was an idiot mistake on my side.
– Mael Razavet
Nov 19 '18 at 16:25
Have you tried to check wich query slick is generates and than this query with explain command postgresql.org/docs/9.3/sql-explain.html?
– Valerii Rusakov
Nov 17 '18 at 18:24
Have you tried to check wich query slick is generates and than this query with explain command postgresql.org/docs/9.3/sql-explain.html?
– Valerii Rusakov
Nov 17 '18 at 18:24
1
1
Found the solution .. The third join was without a condition is simply killing the performance. It was an idiot mistake on my side.
– Mael Razavet
Nov 19 '18 at 16:25
Found the solution .. The third join was without a condition is simply killing the performance. It was an idiot mistake on my side.
– Mael Razavet
Nov 19 '18 at 16:25
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53326151%2fplay-scala-slick-query-incredibly-slow-on-aws-rds%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53326151%2fplay-scala-slick-query-incredibly-slow-on-aws-rds%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Have you tried to check wich query slick is generates and than this query with explain command postgresql.org/docs/9.3/sql-explain.html?
– Valerii Rusakov
Nov 17 '18 at 18:24
1
Found the solution .. The third join was without a condition is simply killing the performance. It was an idiot mistake on my side.
– Mael Razavet
Nov 19 '18 at 16:25