Now, what I am wondering; Is there a better way to do it?
Obviously, for separate servers, sockets are still the way to go. But we have fcgis that we call for data, which are usually on the same system. Is there a better way than a socket to make calls of unknown size on a local system? I have tried UNIX domain sockets, which seem to improve the connection some, but nothing remarkable.
Also, just using sockets I have been playing around. One way to connect is through a C program that you call through the shell, another is a perl module that does a pure perl connect, and the third is to wrap the C code from the program in a SWIG module. I have done all three, and they seem to have improved speed respectively, however... the perl wrapped C module takes the same time in real seconds as the pure perl module, but less system time (according to Benchmark). Am I missing something? Unless there is a noticable difference I am more inclined to travel the pure perl route.
Does anyone have any suggestions as to other approaches I might investigate? I'm running low on ideas...
- Ant
- Some of my
best work - (1 2 3)
In reply to Fastest way to talk to a perl daemon by suaveant
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |