RE: Tower: A REST API implementation on the top of Hivemind

[emrebeyler]

Yeah, unfortunately, if you try a wide ordering on posts or posts_cache it happens since it takes a good amount of time to get the results. Try limiting and narrowing the query for a better performance, for now.

What did you try?

Comments

[wehmoen]

[emrebeyler]

Not with the api, yet :) I will add it if it returns in a feasible time to serve in the api.

[jrawsthorne]

@emrebeyler I added an index for it (took about 15 minutes) with

CREATE INDEX ON hive_posts_cache((json::json->>'app'));

and then I could query like this

SELECT json::json->>'app' as app, author, permlink, body, created_at from hive_posts_cache where json::json->>'app' like 'busy%' order by post_id desc limit 100

[emrebeyler]

This is great @jrawsthorne!

How long does this example query take to complete after the index?

[jrawsthorne]

145ms

[emrebeyler]

Fantastic. Thanks for the tip. I will try adding an additional index after the hive update/migration.

[wehmoen]

[barbara2210]

Muy buena información, aunque tuve que usar el traductor ;)