I’m testing a Linux server for ChatScript on my web page at http://www.turinghub.org/cs/

Just running Harry there, but wanting to add to that script. I’m still learning ChatScript, and trying to learn the syntax for more worthwhile interactions.

I am interested in how many CPU cycles will be involved in running this server.

Robby.

There is no simple answer to this. First, it will depend on the power of your server. I run my server on a cheap Amazon Linux 64-bit machine. How long it takes to respond depends partly on how many rules it has to execute to get an answer. And how complex the rules are (eg doing queries in particular). And this varies based on whether it was doing a rejoinder (few rules) or passed all the way to a quibble (lots of rules). A conversation of 24 consecutive volleys most recently took 13 ms per volley on average for Rose, who is not a simple chatbot and does memorization and queries to learn about the user.

Hey Robby,

I’m running ChatScript on Linux environment on a free account at pythonanywhere.com. there I have 100 seconds of CPU per day and it is more than enough.

From my experience, each volley takes a few milliseconds of CPU. the only part that can take about 1 to 2 seconds is the build process. so if you are looking to save some CPU time you should do it on your local machine and than upload the LIVEDATA to the server.

BTW, I’ve entered your web app and unfortunately, it didn’t work. I would love to see online the results of work people did with ChatScript. hope you’ll fix it.

im also new to CS and when i tryed your link i got this reply

Harry:
Warning: fsockopen() [function.fsockopen]: unable to connect to 162.209.97.239:80 (Connection refused) in /home/fluxoer1/public_html/hub/cs/ui.php on line 47

Fatal error: Error opening socket in /home/fluxoer1/public_html/hub/cs/ui.php on line 49

ive no idea what it means.

In short, that message is informing you that a firewall somewhere between you and the CS server (most likely at the server itself) refused the connection, and thus the request failed.

I also got the same result. It’s noteworthy (to me, at least) that the page from the link looks uncannily like the interface I wrote (well, re-wrote) several months back.

Given that the error message indicates that port 80 was used instead of ChatScript Server’s default of 1024, I would almost bet that a simple configuration change would at least help; and failing that, A configuration change of the firewall would also prove beneficial.