|
From: Walter, S. <Ste...@im...> - 2018-02-15 23:00:05
|
Hello André, in your original e-mail, you wrote: "However, it became too slow and consumes too much processing resources from the vehicles and the server which runs OpenTCS." With 100 bytes every five seconds and no overhead for opening and closing a TCP connection, I don't see any mentionable resource consumption, even with a Raspberry Pi. (These handle streaming videos quite well...) It's not impossible that there is some misunderstanding here, but I don't see what advantage you would gain from adding a database. Best regards, Stefan Von: an...@sp... [mailto:an...@sp...] Gesendet: Donnerstag, 15. Februar 2018 12:41 An: ope...@li... Cc: Walter, Stefan <Ste...@im...> Betreff: Re: [opentcs-discuss] Using Database and OpenTCS Hello Stefan, Thank you for the attention, I have been thinking about using a relational database (MySQL) to improve the performance, once the project may have more than one AGV and we decided to try for a database because we didn't want to be dependent on a single server that would host all client connections. I will try to answer all your questions and hope you can help me. • I believe that the connection is consuming the most part of the resources, once no connection is setted, the resources go fine on their operation. • Yes, I do keep an open communication the whole time and only close it when the vehicle disconnects (i.e: when it shutdows) • I am using messages which are encoded using JSON and the messages do not exceed more than 100 bytes. • The messages are exchanged once OpenTCS releases a new ' MovementCommand ', so, it depends on the time the AGV reaches the intended position (about 5 seconds or more) Also, just to mention, the client is setted using python language, once it runs on a Raspberry PI3. Looking forward to your reply Best regards. André |