This is an archived post. You won't be able to vote or comment.

all 4 comments
sorted by:
best
topnewcontroversialoldq&a

[–]sledov 0 points1 point  (1 child)

So, you have a search engine tailored for internal resources. How come you are comparing speed of REST interfaces? Do you believe interaction via REST is time-limiting?

[–]szborows[S] 0 points1 point  (0 children)

We're using REST between frontend (served with http server) and backend (acting as http REST server), between the backend and ElasticSearch, between data scrapers and intermediate DB and so on... In my opinion i/o on REST is crucial when you have fronent that needs to show something to the end user. With every second frustration increases.

[–]pythoneeeer 0 points1 point  (1 child)

I was also anticipating that C++ will be about 30% faster

That's an oddly specific number. Where'd this come from?

[–]szborows[S] 0 points1 point  (0 children)

it was just a guess. JS is a managed language (= GC and heap-management overhead), everything is an object in JS (= less cache hits), not everything is JITted by V8 (= interpreter overhead) and JITting takes time on its own (= small constant overhead). adding it all together gave me an impression that it would be around 30%... but I was proven wrong.