Testing recommender sample

GSQL
#1

When I read GSQL Language Reference, I tried the Recommender samples. I installed the log similarity and cosine similarity queries , with one named recommend_message and the other recommend_message2.

So I tested (“Viktor”, “Akhiezer”) and (“Adriaan”, “Jong”) with those two queries as the article mentioned.

When I use “RUN QUERY” mode to test, it seems all OK. That means the following are all OK.

  1. RUN QUERY recommend_message (“Viktor”, “Akhiezer”) OK
  2. RUN QUERY recommend_message (“Adriaan”, “Jong”) OK
  3. RUN QUERY recommend_message2 (“Viktor”, “Akhiezer”) OK
  4. RUN QUERY recommend_message2 (“Adriaan”, “Jong”) OK

When I use “INTERPRET QUERY” mode to test, the first one is ok,and the second one exceeded the default query timeout. and the other two more test cases are all failed as the same reason.
5) INTERPRET QUERY recommend_message (“Viktor”, “Akhiezer”) OK
6) INTERPRET QUERY recommend_message (“Adriaan”, “Jong”) overtime
7) INTERPRET QUERY recommend_message2 (“Viktor”, “Akhiezer”) overtime
8) INTERPRET QUERY recommend_message2 (“Adriaan”, “Jong”) overtime

And after that, the terrible thing happened, when I use “RUN QUERY” again, the test cases are all overtime !!!

All I have to do is to restart the tigerGraph DB again…

Can anybody tell me why?

#2

OK, I user 8GB machine, with OS CentOS 7.9. and the version of tigerGraph is 3.5.3.When I restart the DB and tried again, ther same thing happened.

I think maybe when the first case overtime happened, there is some exceptions with the engine, and then it would lost the functionality to respond any input again.

#3

I left the INTERPRET QUERY recommend_message (“Adriaan”, “Jong”) in the last, and test again.

  1. RUN QUERY recommend_message (“Viktor”, “Akhiezer”) OK

  2. RUN QUERY recommend_message (“Adriaan”, “Jong”) OK

  3. RUN QUERY recommend_message2 (“Viktor”, “Akhiezer”) OK

  4. RUN QUERY recommend_message2 (“Adriaan”, “Jong”) OK

  5. INTERPRET QUERY recommend_message (“Viktor”, “Akhiezer”) OK

  6. INTERPRET QUERY recommend_message2 (“Viktor”, “Akhiezer”) OK

  7. INTERPRET QUERY recommend_message2 (“Adriaan”, “Jong”) OK

  8. INTERPRET QUERY recommend_message (“Adriaan”, “Jong”) overtime

And then all cases could not be done OK now…

#4

Grant,
Thanks for reporting this issue.
It seems that when this particular query and inputs are used
recommend_message (“Adriaan”, “Jong”)
it is overtime and does not recover. Is that your understanding as well?

#5

Yes,that’s it.Thanks for your reply.