Hello David!
Your project seems to be very interesting, could you elaborate a bit more?
So much thank you!
I will definitely be happy to elaborate more on it via a skype call: I could share the screen and show what I m boiling in the pot :D
Back to your reply now:
Yes, I was mainly testing during time both Europe and USA are connected.
However, I am experiencing this type of delay from my laptop; maybe on deployment will speed up cause is my home network creepy?
I am concerned because I need to first fetch results from Wikipedia, then elaborate with my own data (that is fast enough <200ms) and then push it to the client. That is the reason of why I will put it server side and not client-side.
I need search generator only as first entry point: imagine you need to search for a topic, but you don't know exactly what. Imagine an input form, you type in some keywords, select one among results, and then you start your session.
I cannot estimate exactly the amount of FST query I need; let's say each user will need a search generator only once per session.
Maybe 30 user per seconds concurrent would be a good reference (it 's same number Parse of Facebook provide, Firebase up to 100... so maybe I could relay on similar order of magnitude...)
If I can provide people with a smooth user experience on search, that will be interesting because I could free resources up : I may extend a test of knowledge discovery to other languages, too.
If the first user experience was too slow (~1.3s + bandwith transmission ~1.5+ per query) that could become critical.
I don't need search generator to operate in batch, or to track changes.
It just serve the user to find a topic as entry point for discovery.
I cannot use 'Opensearch' because it does not provide _IDs ; also, it searches against titles only.
Would it be possible to reserve somehow bandwith or requests for a domain?