01-03-2017
I asked what the operating systems were in post#6.
If one of them is Windoze it would explain everything; period.
Windoze is hopeless at transferring very large files. It starts off fine but then gets slower and slower and slower, down to a crawl.
Are You Seeing Slow Windows 7 Network Performance?
And I'm not aware of any Windows version with this problem fixed.
Last edited by hicksd8; 01-03-2017 at 12:16 PM..
This User Gave Thanks to hicksd8 For This Post:
10 More Discussions You Might Find Interesting
1. Programming
After my previous thread, I think I found out what causes the long delays.
I run this program on several Linux computers, and the sometimes (after the file with the arrays becomes big) the fwrite takes between 100 ms to 900 ms.
This is very bad for me, as I want a timer to halt each 30 ms.... ... (5 Replies)
Discussion started by: inna
5 Replies
2. Shell Programming and Scripting
Hi all,
I wrote this shell script to validate filed numbers for input file. But it take forever to complete validation on a file. The average speed is like 9mins/MB.
Can anyone tell me how to improve the performance of a shell script?
Thanks (12 Replies)
Discussion started by: ozzman
12 Replies
3. AIX
Hi,
I have NTP configured:
vi /etc/ntp.conf
broadcastclient
server 128.127.1.3
driftfile /etc/ntp.drift
tracefile /etc/ntp.trace
# xntpdc
xntpdc> sysinfo
system peer: 128.127.1.3
system peer mode: client
leap indicator: 00
stratum: 12
precision: ... (0 Replies)
Discussion started by: victorcheung
0 Replies
4. Linux
Hi,
I am trying to login using ssh on Red Hat Linux 5 server,
The password appears immediately but after I enter the password it takes about 90 seconds to login completely.
Please suggest what changes require?
Regards,
Manoj (4 Replies)
Discussion started by: manoj.solaris
4 Replies
5. UNIX for Dummies Questions & Answers
Hello,
like the title says, how can i measure the time it takes to load a module in Linux, and how how can i measure the time it takes to load a statically compiled module.
/Best Regards Olle
---------- Post updated at 01:13 PM ---------- Previous update was at 11:54 AM ----------
For... (0 Replies)
Discussion started by: ollebanan
0 Replies
6. UNIX for Dummies Questions & Answers
We are running unix. After a reboot of the server we have found that changing password takes a long time. if type in passwd "username" you can type in the 1st instance of the password , press enter , then it will wait for about 3 minutes before bringing up the confirm password line typing it in... (4 Replies)
Discussion started by: AIXlewis
4 Replies
7. Shell Programming and Scripting
Dear experts
I have a 200MG text file in this format:
text \tab number
I try to sort using options -fd and it takes very long! is that normal or I can speed it up in some ways?
I dont want to split the file since this one is already splitted.
I use this command: sort -fd file >... (12 Replies)
Discussion started by: voolek
12 Replies
8. Red Hat
When I am trying to login to a server using Putty ssh from my windows xp machine it is taking too much time for login.
My server name is http2 and when I enter this address into putty I immediately get
login as:
screen, but after I put my username root and enter the cursor moves downwards... (14 Replies)
Discussion started by: abhilashkrishn
14 Replies
9. UNIX and Linux Applications
Hi,
we currently having a issue where when we send jobs to the server for the application lawson, it is taking a very long time to complete. here are the last few lines of the database log.
2012-09-18-10.35.55.707279-240 E244403536A576 LEVEL: Warning
PID : 950492 ... (1 Reply)
Discussion started by: techy1
1 Replies
10. Shell Programming and Scripting
Hi,
I wish to check the return value for wget $url.
However, some urls are designed to take 45 minutes or more to return.
All i need to check if the URL can be reached or not using wget.
How can i get wget to return the value in a few seconds ? (8 Replies)
Discussion started by: mohtashims
8 Replies
LEARN ABOUT NETBSD
rump_sp
RUMP_SP(7) BSD Miscellaneous Information Manual RUMP_SP(7)
NAME
rump_sp -- rump remote system call support
DESCRIPTION
The rump_sp facility allows clients to attach to a rump kernel server over a socket and perform system calls. While making a local rump sys-
tem call is faster than calling the host kernel, a remote system call over a socket is slower. This facility is therefore meant mostly for
operations which are not performance critical, such as configuration of a rump kernel server.
Clients
The NetBSD base system comes with multiple preinstalled clients which can be used to configure a rump kernel and request diagnostic informa-
tion. These clients run as hybrids partially in the host system and partially against the rump kernel. For example, network-related clients
will typically avoid making any file system related system calls against the rump kernel, since it is not guaranteed that a rump network
server has file system support. Another example is DNS: since a rump server very rarely has a DNS service configured, host networking is
used to do DNS lookups.
Some examples of clients include rump.ifconfig which configures interfaces, rump.sysctl which is used to access the sysctl(7) namespace and
rump.traceroute which is used to display a network trace starting from the rump kernel.
Also, almost any unmodified dynamically linked application (for example telnet(1) or ls(1)) can be used as a rump kernel client with the help
of system call hijacking. See rumphijack(3) for more information.
Connecting to the server
A remote rump server is specified using an URL. Currently two types of URLs are supported: TCP and local domain sockets. The TCP URL is of
the format tcp://ip.address:port/ and the local domain URL is unix://path. The latter can accept relative or absolute paths. Note that
absolute paths require three leading slashes.
To preserve the standard usage of the rump clients' counterparts the environment variable RUMP_SERVER is used to specify the server URL. To
keep track of which rump kernel the current shell is using, modifying the shell prompt is recommended -- this is analoguous to the visual
clue you have when you login from one machine to another.
Client credentials and access control
The current scheme gives all connecting clients root credentials. It is recommended to take precautions which prevent unauthorized access.
For a unix domain socket it is enough to prevent access to the socket using file system permissions. For TCP/IP sockets the only available
means is to prevent network access to the socket with the use of firewalls. More fine-grained access control based on cryptographic creden-
tials may be implemented at a future date.
EXAMPLES
Get a list of file systems supported by a rump kernel server (in case that particular server does not support file systems, an error will be
returned):
$ env RUMP_SERVER=unix://sock rump.sysctl vfs.generic.fstypes
SEE ALSO
rump_server(1), rump(3), rumpclient(3), rumphijack(3)
HISTORY
rump_sp first appeared in NetBSD 6.0.
BSD
February 7, 2011 BSD