Im quite new to scripting and would like a bit of assistance with trying to speed up the following script. At the moment it is quite slow....
Do you realize you're never clearing that XML file? It's just growing and growing every loop!
Anyway, you can put all that text in a here-document to avoid 99 echo calls writing to the same file:
Instead of running the same thing 9 times to do 9 queries, you could probably run the same thing once to handle all nine queries, tying them directly in with a pipe.
What is this 'database query which uses file'? I suspect that's going to be the limiting step here and we can't tell you how to rewrite it without seeing it.
Hello,
I have a Supermicro server with a P4SCI mother board running Debian Sarge 3.1. This is the "dmidecode" output related to RAM info:
RAM speed information is incomplete.. "Current Speed: Unknown", is there anyway/soft to get the speed of installed RAM modules? thanks!!
Regards :)... (0 Replies)
hi i have a script that is taking the difference of multiple columns in a file from a value from a single row..so far i have a loop to do that.. all the data is floating point..fin has the difference between array1 and array2..array1 has 700 x 300= 210000 values and array2 has 700 values..
... (11 Replies)
Hey together,
You should know, that I'am relatively new to shell scripting, so my solution is probably a little awkward.
Here is the script:
#!/bin/bash
live_dir=/var/lib/pokerhands/live
for limit in `find $live_dir/ -type d | sed -e s#$live_dir/##`; do
cat $live_dir/$limit/*... (19 Replies)
I have a script that processes a fair amount of data -- say, 25-50 megs per run. I'd like ideas on speeding it up. The code is actually just a preprocessor -- I'm using another language to do the heavy lifting. But as it happens, the preprocessing takes much more time than the final processing... (3 Replies)
I analysed disk performance with blktrace and get some data:
read:
8,3 4 2141 2.882115217 3342 Q R 195732187 + 32
8,3 4 2142 2.882116411 3342 G R 195732187 + 32
8,3 4 2144 2.882117647 3342 I R 195732187 + 32
8,3 4 2145 ... (1 Reply)
Hi Guys,
I have a script that I am using to convert some text files to xls files. I create multiple temp. files in the process of conversion. Other than reducing the temp. files, are there any general tricks to help speed up the script?
I am running it in the bash shell.
Thanks. (6 Replies)
I had written a perl script to compare two files: new and master and get the output of the first file i.e. the first file: words that are not in the master file
STRUCTURE OF THE TWO FILES
The first file is a series of names
ramesh
sushil
jonga
sudesh
lugdi
whereas the second file (could be... (4 Replies)
hey guys i have a perl script wich use to compare hashes but it tookes a long time to do that so i wich i will have the soulition to do it soo fast
he is the code
<redacted> (1 Reply)
Hi
I have written a shell script which will test 300 to 500 IPs to find which are pinging and which are not pinging.
the script which give output as
10.x.x.x is pining
10.x.x.x. is not pining
-
-
-
10.x.x.x is pining
like above.
But, this script is taking... (6 Replies)
Hello,
I am basic level shell script developer. I have developed the following script. The shell script basically tracking various files containing certain strings. I am finding options to make the script run more faster. Any help/suggestion would be appreciated :)
#! /bin/bash
# Greps for... (6 Replies)
Discussion started by: Bhanuprasad
6 Replies
LEARN ABOUT DEBIAN
frontier::responder
Frontier::Responder(3pm) User Contributed Perl Documentation Frontier::Responder(3pm)NAME
Frontier::Responder - Create XML-RPC listeners for normal CGI processes
SYNOPSIS
use Frontier::Responder;
my $res = Frontier::Responder->new( methods => {
add => sub{ $_[0] + $_[1] },
cat => sub{ $_[0] . $_[1] },
},
);
print $res->answer;
DESCRIPTION
Use Frontier::Responder whenever you need to create an XML-RPC listener using a standard CGI interface. To be effective, a script using
this class will often have to be put a directory from which a web server is authorized to execute CGI programs. An XML-RPC listener using
this library will be implementing the API of a particular XML-RPC application. Each remote procedure listed in the API of the user defined
application will correspond to a hash key that is defined in the "new" method of a Frontier::Responder object. This is exactly the way
Frontier::Daemon works as well. In order to process the request and get the response, the "answer" method is needed. Its return value is
XML ready for printing.
For those new to XML-RPC, here is a brief description of this protocol. XML-RPC is a way to execute functions on a different machine. Both
the client's request and listeners response are wrapped up in XML and sent over HTTP. Because the XML-RPC conversation is in XML, the
implementation languages of the server (here called a listener), and the client can be different. This can be a powerful and simple way to
have very different platforms work together without acrimony. Implicit in the use of XML-RPC is a contract or API that an XML-RPC listener
implements and an XML-RPC client calls. The API needs to list not only the various procedures that can be called, but also the XML-RPC
datatypes expected for input and output. Remember that although Perl is permissive about datatyping, other languages are not.
Unforuntately, the XML-RPC spec doesn't say how to document the API. It is recomended that the author of a Perl XML-RPC listener should at
least use POD to explain the API. This allows for the programmatic generation of a clean web page.
METHODS
new( OPTIONS )
This is the class constructor. As is traditional, it returns a blessed reference to a Frontier::Responder object. It expects arguments
to be given like a hash (Perl's named parameter mechanism). To be effective, populate the "methods" parameter with a hashref that has
API procedure names as keys and subroutine references as values. See the SYNOPSIS for a sample usage.
answer()
In order to parse the request and execute the procedure, this method must be called. It returns a XML string that contains the
procedure's response. In a typical CGI program, this string will simply be printed to STDOUT.
SEE ALSO perl(1), Frontier::RPC2(3)
<http://www.scripting.com/frontier5/xml/code/rpc.html>
AUTHOR
Ken MacLeod <ken@bitsko.slc.ut.us> wrote the underlying RPC library.
Joe Johnston <jjohn@cs.umb.edu> wrote an adaptation of the Frontier::Daemon class to create this CGI XML-RPC listener class.
perl v5.10.1 2002-08-03 Frontier::Responder(3pm)