Ftp too slow: pharlap and linux ftp problem

Hi all,
my problem seems very strange.
I work with a rt system (PXI 8187 with pharlap os). I have to retrieve several log files that can be very heavy (100 MB or more).
When I retrieve these files using Internet Explorer the ftp has a transfer rate of 500 KB/s ca. If I use SUSE Linux the transfer rate is 10 KB/s, that is not acceptable.
Moreover if I use a windows client onto SUSE Linux (using VMWare) the client present a transfer rate of 500 KB/s.
Finally the SUSE ftp client can retrieve from other FTP server (Linux) with a good transfer rate (1 MB/s).
So I can't understang where is the problem: windows can retrieve from pharlap, linux can retrieve from linux, windows onto linux can retrieve from pharlap, linux CAN'T (because too slow) retrieve from pharlap.
can someone help us?
thanks all.
Andrea

Hi Anmol,
That's an interesting issue, I currently have some cRIO's sitting on my desk and would love to help you get to the bottom of this issue, could you let me know a few things:
1. Operating systems the same?
2. cRIO controller model & revision (revision is the first letter in the part number i.e. 111111C-00L would be rev C)
3. Network speeds of both laptop ethernet ports & the chipsets for these (via device manager)
4. Do you have another PC you could check this on to narrow it down to the laptop
5. Have you always had this issue?
Thanks,
Applications Engineer

Similar Messages

My iMac 8.1 was slowing down and had permissions problems. I backed everything up, and then re-installed. Now all I get is a black screen. Power+D gives me a hardware error message: HDD-1336. Help!

My iMac 8.1 (10.6.8 ) was slowing down and had recurrent permissions problems, mostly with Java. I backed everything up, and then re-installed from time machine. Now all I get is a black screen which says I need to reboot. Power+D gives me a hardware error message: 4 MOT/1/40000003: HDD-1336 or HDD-1327. When I reboot from the OSX CD and start disc utilities everything checks out OK. When I reload 10.5.2 from the OSX CD everything seems to work OK and no more permissions problems. But then I loose all my email and safari stuff. Anyone have any ideas short of going back to my old PC?

DonM. wrote:
Hi
Thanks for the help. No point in fooling around with it any more. Will I be able to use it as a monitor if I get a mimi mac?
Cheers. Don
No unfortunatley it's too old, you are referring to Target Display Mode which became avialble in 2009, your 2008 needs to have the HD replaced. I'd still do that if everything else is OK or you can simply buy a new MM and display or even a new iMac or an Apple refurbished iMac to save money.

WebObjects Java Client-JNLP fine on OS X and Linux, Windows problem

Hi,
I have been making a somewhat fruitful exploration into WebObjects Java Client development in order to get my nice IB interfaces for prototypes functional and deployed in a cross platform environment.
I have made some good strides in figuring out the semi-documented process of Java/IB integration, and how to build (including adding external libraries) and deploy onto a server (if anyone else is interested I will share; perhaps a blog is deserved), and though I am able to run it from both Mac OSX and Linux clients on the network (the Linux interface currently looks like garbage but will work on that), when I try to run it on windows I immediately get the following error tab in General:
An error occurred while launching/running the application.
Title: ProfessionalTradingRAD
Vendor: Vendor
Category: Download Error
Unable to load resource: http://g5.nl.imc.local:2002/cgi-bin/WebObjects/ProfessionalTradingRAD.woa/eowebs tart/com.webobjects.eodistribution._EOWebStartAction/webStart/JavaClient.jnlp
and in the Exception tab it reads:
JNLPException[category: Download Error : Exception: java.io.IOException: rename failed in cache to: C:\Documents and Settings\alko\Application Data\Sun\Java\Deployment\javaws\cache\http\Dg5.nl.imc.local\P2002\DMcgi-bin\DMW ebObjects\DMProfessionalTradingRAD.woa\DMeowebstart\DMcom.webobjects.eodistribut ion._EOWebStartAction\DMwebStart\AMJavaClient.jnlp : LaunchDesc: null ]
at com.sun.javaws.cache.DownloadProtocol.doDownload(Unknown Source)
at com.sun.javaws.cache.DownloadProtocol.getLaunchFile(Unknown Source)
at com.sun.javaws.LaunchDownload.getUpdatedLaunchDesc(Unknown Source)
at com.sun.javaws.Launcher.downloadResources(Unknown Source)
at com.sun.javaws.Launcher.handleApplicationDesc(Unknown Source)
at com.sun.javaws.Launcher.handleLaunchFile(Unknown Source)
at com.sun.javaws.Launcher.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
It looks to me like the problem is with trying to rename the directory to a name with multiple periods, which works on UNIX but not on Windows. Is this a familiar problem? Is there any workaround/solution or any intent to fix?
Thanks
--Alex Kogon
Mac OS X (10.4.6)

open terminal and run runinstaller again...
don't double click and execute runinstaller....
From Achi Cheng

System slows down and power up problems

Hi,
I have a Rev A G5 iMac (1.8Ghz, 1.5GB Ram) which has been working fine since purchased in 05.
Over the 5-6 weeks we have been experiencing system slow downs. All applications will start running slower and slower (not heavy usage, mail, safari, BT client running and occasionally iMovie) to the point have to restart.
But when restarting the iMac it will not power up, it starts and 1 sec later shuts down. So I leave for a while and try again, and it will work although the fan is extremely loud.
I was having to restart every few days but now its to the point of a few times a day.
have run hardware test and all is fine...and as do not have applecare want to see if can do anything myself before taking in for a quote/repair.
Oh another thing, the superdrive will not burn via finder anymore only via toast...that started at the same time as the rest.
many thanks
Zara

Hi Zara - have you tried opening the back and vacuuming out several years accumulation of dust? You can also try resetting the PRAM and the SMU and see if that helps.
Please post back,
Miriam

No Reason For Disk Too Slow Error, any ideas?

Ok,
So I've used Garageband for years from iLife 06 and up and I've never had an issue with any Garageband until now. Here's the deal, I still get the disk too slow error, and there is no explanation. Below is my computer config:
COMP I'M USING:
Macbook Pro 13 inch
OS X Mavericks
Intel Core 2 Duo (1st unibody)
4 GB of RAM MAX
BRAND NEW Hybrid 7200 RPM Drive Installed 500GB total, 300 GB FREE
NO Other programs are open.
I use Garageband for recording songs but mostly now for recording podcasts. So the track I am using is normally 1 hour in duration. I can't seem to skip around, from minute 1 to minute 54 and edit at my whim without beach ball and timeing out getting the disk to slow error I never had this issue before, I either get the disk to slow error when trying to navigate large gaps of time in the podcast as I said earlier or even during RECORDING a podcast it'll simply say disk to slow, stop recording and occassionally say there are too many tracks in use, when I only record using 1 track of audio.
How can this be possible? Even my old G4 allowed me to jump all over the timeline with no issues. It seems there is some kind of flaw in the software. And yes, I just restored OSX Mavericks to my brand new Hybrid Hard drive, so there's no explanation as there are no disk errors or permissions errors of any kind.
I'd rather not hookup an external drive to record too as that seems silly when I've never had too before. If this "modern" computer can't do something that my old G4 ibook can do, don't you think we're going in the wrong direction with this program?
I've heard of so many people having this issue, and I thought upgrading my OS and getting a new HD would help but it hasn't. I'm at wits end with this issue.
Any advice would be helpful, thank you.

There are a few other reports of problems with 10.6.7
Some audio device(s) inputs have ceased working, a few disk to slow messages...etc. I don't see the wisdom of upgrading a working DAW system if that's it main function. OSX has to support a lot of different hardware now, many, many Intel motherboard and/or processor revisions... it's not going to be as smooth sailing as it used to be.
pancenter-
Here's a search over the past 90 days.
http://discussions.apple.com/search.jspa?threadID=&q=Disktoslow&objID=c231&dateRange=last90days&userID=&numResults=15&rankBy=10001

Disk too slow error when using M-Audio Oxygen 49 keyboard

I bought the M-Audio Oxygen 49 keyboard. And when I plug it into my MacBook Pro to do some playing, the project will record for maybe a minute but then I get a 'disk too slow' error and the recording stops. This happens every single time, no matter if there's 30 tracks or 1 track on the recording. I know that it is the keyboard causing the error because I am currently working on a 59 track piece that has effects on almost every track and my setup doesn't even blink. (well it'll pinwheel for a second when I hit record sometimes, but the CPU and disk meters don't ever get near red-line levels).
What on earth is causing this stupid keyboard to cause this problem, and how do I fix it? It's clearly the keyboard. When I unplug it and record a live track on a project that just gave me the 'disk too slow' error, everything works just fine!
Grr...
Any help is appreciated, thanks!
Edit: I have the MBP plugged via firewire into an Echo Audiofire and then into a WD hard dtive (at 7200 RPM). The keyboard is USB into the MBP.
Message was edited by: Zombie Flanders
Message was edited by: Zombie Flanders

hi
i spoke with Apple pro application support staff who confirmed that the Tascam 1884 patch for 10.4.10 is the cause of the problem. The apple boot drive can reliably record 1 channel of audio under normal circumstances. Apple staff described the situation as "unfortunate" and recommended to wait for Tascam to release 10.4.10 compatible drivers.
For anyone interested in the technical background, the Tascam 10.4.10 patch DOWNGRADES the audioFW component (messing with kernel headers etc.). This compromises the OS's ability to correctly communicate with FW devices.
I had tried recording to a firewire 800 drive, but all FW IO is affected by the 10.4.10 Tascam patch: Logic simply didn't record anything to disk when I tried this, and the machine became unresponseive. I do not recommend anyone attempt recording to a FW drive with the Tascam drivers installed.
I have recorded circa 400 hours of single channel 96K 24bit audio to my internal Macbook Pro boot drive using the same software/configuration under 10.4.9 without a single glitch. I do recognise that when requiring heavy disk IO it is not advisable to record to the boot drive. However, 1 channel of audio can be reliably recorded if the system is well maintained.
Thanks to all for your comments and suggestions.

How do i stop a download when it is too slow?

How do I stop a download when it is too slow?

Solved my own problem: Go to the sidebar on i Tunes to "Downloads" and click on this. It will show current downloads. Click on the download you wish to delete and then click on "delete" in the File menu. You can also shift-click to delete a range of items.

4 to 4.1 - too slow to use.

Since upgrading to 4.1 LR has become too slow to use.
The problem lies primarily, but not restricted to, the noise reduction sliders. The luminance slider specifically.
Unless I can fix something I will have to return to an older version, Im actually thinking of going back to 3.6 which worked fine on my machine - AMD E2, Dual Core graphics, 4gm RAM.
Please help.

The queries are the same across all three database platforms and have been examined by our dba's and run through SQL Server optimizer to get the access path. All queries are very simple...the system was originally written in Btrieve. It is "record at a time" in nature. The program that does the screen refresh does three seperate queries...all something like, select * from tablename where key = 'abc'. The program then combines the data into a single record and returns the results. Like I said...SQL Server 1 second. Each of the three tables has 30,000 records, all with unique keys. The data returned to the application is probably 50 records, each 200 bytes...all character data. All tests were done with the same workstation on the same LAN....I don't think LAN latency is the problem here. Using other query tools, the response back is good, as expected.
Another example...at application startup, we load all of the metadata (columns, primary key segments and index segments) into memory using the standard odbc api calls...SQLColumns, SQLPrimaryKeys and SQLStatistics. SQL Server loads this in maybe 8-10 seconds while Oracle loads in 15 minutes at best. These queries we don't control and it is still unbelievably slow. Again, using the ODBCTEST utility, the results for these api's come back pretty quick.
If it is our application causing the problem in some way then it should be equally slow across all platforms, right?
By the way, we had one of your Oracle Consultants in house trying to solve the metadata problem and he was unable to find any problem in our application and had no answers for us.
Thanks for the quick response.
Lon Diehl

Disc is too slow or system overload

"Disc is too slow or system overload"
right in the middle of a project. stupid question. what can i do? won't even play. can't even bounce it.

Was dealing with that, among other system/disk response issues last weekend. This weekend I researched it extensively and found 2 things that, knock on wood, so far have seemed to resolve my issues. One Mac white paper suggested that when using an external drive, you must format it as MAC Extended, and NOT include journaling. This paper was dated in 2006, but the theory made sense to me, so I tried it. BTW, it also emphasizes that you NOT get rid of journaling on the main HDD of the computer. The other thing I stumbled across was a little download calls "ProKitUpdate 4.5". It is supposed to make your 'professional' apps run smoother. I also downloaded and installed that. I then set up a test with 8 inputs, recording at 48K x 24 bit (what I was doing weekend before last), and recorded for about 2 hours. During that test, I had no beachballs, no dropouts, no 'disk is too slow' errors, and as a matter of fact, no errors at all. At this point, I'm feeling more comfortable with the setup, but am still planning on some more testing before I assume the problem won't happen again.
Charley

Too slow FTP DW CS3 on a Mac?

If your FTP transmissions in Dreamweaver CS3 on MacOsX are
too slow, try the following:
Go to » Preferences » Invisible Elements » and
de-select every marked select-box on this page!
Changing these settings makes a huge difference in
Dreamweaver CS3 performance and FTP-speed.

There is no command line interface in Dreamweaver. It's a tool for editing web pages.
However, you can use Dreamweaver to set the permissions on web pages on your remote server like this:
In the Files panel, select Remote view from the drop-down menu at the top right.
Select the file(s)/folder(s) for which you want to change the permissions.
Right-click and select Set Permissions from the context menu.
Set the permissions in the dialog box that opens.
As the dialog box warns you, this command does not work on all servers. If your remote server won't allow you to change permissions through Dreamweaver, you need to log into your hosting company's control panel, and change the permissions there. If you don't know how to do it through the control panel, ask your hosting company for help, as the method depends on the control panel used.

Dreamweaver CS3 (9) maxed CPU slow performance and FTP issues.

Dreamweaver CS3 (9) maxed CPU slow performance and FTP
issues.
Never mind...I found it.
Of course I have all the firewall, worm, scanning, phishing
filtering, full time protect, and everything else turned off when I
am working on a remote/testing site however I found the Symantec
antivirus email scan being enabled (doesn't it just interact with
my email program?) was getting in the way of DW9 ftp operations,
causing some lagging that was putting DW9 into an unstable mode
during and immediately after (10 seconds) ftp operations.
The CPU still spikes to 99% during ftp functions but DW9
works even though it's likely taxed to the max but when I turn off
email scan DW9 returned to a functioning state during ftp and
remote file view. Whatever it takes huh?
PS: email scanning only never effected DW8.02
My System Info: properly configured (as in: everything works
or I fix it) Toshiba - XP pro SP2 – Pentium 4 - 2.3GHz
– 1.5 GB ram – Intel extreme graphics card 64 MB ram
– Apache 2.2 server – PHP 5 – MySQL 5 -
phpMyAdmin – Dreamweaver 8.02 – Interakt Kollection
3.7.1 – Dreamwweaver 9 - DeVtoolbox – Flash –
GoLive - Photoshop - ImageReady – Illustrator – Acrobat
– CuteFTP – Putty SSH - blabla...)

Thanks for the response. I managed to Google the 'nobody' account and found the explanation.
As you say, I assumed the 'syslogd' process had to do with system logs. I did check the console and couldn't find anything of particular interest in the logs.
I'll continue to monitor but if anyone has any further suggestions please post.
One thing that might also have an impact... my available drive space is now down to less than 5gb (runs anywhere between 1gb and 5gb free depending on what I'm running). I know this causes problems for Parallels as it keeps moaning at me, but would it cause any problems with OSX?
Thanks again,
Tom

"LOGIC PRO X: Disk is too slow or System Overload. (-10010)" This is the message that I was having since two weeks ago with my Logic 9. I updated two days ago to Logic X and I am still having the same problem.

"LOGIC PRO X: Disk is too slow or System Overload. (-10010)" This is the message that I was having since two weeks ago with my Logic 9. I updated two days ago to Logic X and I am still having the same problem.
I recently formatted my computer. In other words, I'm not using too much memory of my HD. My Memory Ram is 8GB.

dandotcraig wrote:
A week before logic X comes out it starts bugging out... i deleted a bunch of stuff on my HD and cleaned up everything... didnt fix anything... then logic x came out and I though oh i better update that will fix everything... and im still having the same problems... its rediculous.
Umm,, no offence... but what is ridiculous... is you didn't troubleshoot the original problem but instead you assumed it was a LP9 problem so you updated to LPX which is still in its early days and is likely to be less stable than LP9... rather than more so!
So.. Here's the thing....
LP9 was working fine and then stopped working normally according to you. Therefore what changed at the time LP9 stopped working normally?
Here are just a few ideas to think about.. for around the time this started..
Did you update Logic Pro 9... OS X... Drivers for Midi/Audio or other connected devices?
If you did, did you then restore from a backup you made prior to these problems occuring and what happened when you did so? (assuming you do make backups of your system?)
Did you install any new Apps on your Mac?
Did you add a new Hard Drive? How is it formatted?
Did you start recording or creating music in a different way to how you used to before the problem started?
Have you started using a different SI or FX plugin or plugins.. More or different FX for example.. Did you install a new version of a plugin?
Is all your software legal? (Have to ask because some people install all kinds of illegal plugins and whatever else.. and have no idea how the 'cracks' work or what they might affect/mess up/conflict with in the process)
Have you looked at the System logs to see if anything is happening out of the ordinary when you get these messages?
Have you looked at OS X's Activity monitor to see if any app or routine is kicking in hard when you get this issue?
Basically, you need to think about and look for what changed... because something apparently changed to suddenly cause these issues...given you said you didn't have them until a certain timeframe and some of the questions above, I hope, will get you thinking..
....and maybe a few of the others here will come up with other ideas and suggestions to help you...
Good luck and let us know how you got on...

I allowed Apple updates about two weeks ago and now Safari is way too slow. I have tried using Airport and Ethernet and the problem is the same. Yesterday, I updgraded to Safari 5.1 and the problem is now worse. Any solutions?

I allowed Apple updates about two weeks ago and now Safari is way too slow. I have tried using Airport and Ethernet and the problem is the same. Yesterday, I upgraded to Safari 5.1 and now the problem is worse. Any solutions?

I can't stand peremptory affirmations like "Nothing is wrong with Safari".
Thousands of users can't be wrong (see the discussions).
If I read you the right way, it's never software' fault, it's the user who's the culprit.
Amazing!
In this very case, the fact is we can't give to "christinefromfonthill" a good solution because weren't sitting in front of her Mac.
You give her a good advice which could, perhaps, lead to an improvement.
But must also admit that Safari is a very slow browser compared to Firefox or Chrome.
And you can't ignore all the problems which arose when upgrading to Lion and were related to the new build and specs of Safari 5.1.
The best example is the apparition of "garbage type" (use of Last Resort font) when reading numerous sites. This never occured before and is the direct consequence of Safari compliance to Web Open Type. This standard prohibits the use of Type 1 Postscript Fonts and is the reason why so many people are in trouble.
I use a Mac for more than 25 years.
I am a very "clean" user who hates the bells and whistles of third party.
My Mac is always up-to-date and despite all my Mac loving care, I run into some problems.
Imagine the nightmare which can occurs for the vulgum pecus who isn't, by definition, a power user aware of all the requirements for running a System in optimal conditions.
May be Safari is one step in advance on its time but lambda users are paying the price for it.

How do I fix the problem 'disk is too slow' and what does it mean anyway?

I'm transferring casete tapes to the Mac via the input line. I've transferrred nearly 100 with no prouble, but sudddenly today two things have gone wrong (see separate question for the other one). This one is that suddenly the error message 'Disk is too slow' comes up. also the track (the top one, not the bottom edit section one) is bright red instead ofthe usual dark purple.
What's gone wrong and how do I fixit?

Sorry about the lack of terms: lazy of me I admit. Having read up Garageband Help, I think I've got the answers. Yes, by the top part I mean the track in the timeline. The bottom part is the same track showing up in what is headed the 'Audio Region' The bright red is the colour the track is in the timeline during recording, and it stays like that until after stopping recording I click somewhere in the timeline section (not necessarily on the track itself) at which time it just goes the normal kind of dull greyish colour an unselected region does.
Thanks for telling me how to see the HD info. Its 250GB, of which I've used about 23GB. The first computer I worked on as a programmer back in 1962 had a 400KB drum (the first disks didn't arrive until 1963) as its random access backing store - and yes, that is a K. The machine also came with 12KB of RAM and 4 tape decks, was the size of a hotel kitchen, and cost about $200,000. You young people don't know how lucky you are

PixelGrabber is too slow and has memory problems!

Have any of you figured out a way to get pixels from an Image
WITHOUT using PixelGrabber??
PixelGrabber is really slow -- is a memory hog -- and has other problems
that cause me to need another way to get pixels from an image.
Does anyone else have a way to get the pixels directly from an Image
without using PixelGrabber?
Ken Warner

Hi, there are ways to do it if you can live with certain restrictions.
            BufferedImage img=new BufferedImage(32,32,BufferedImage.TYPE_INT_ARGB);
            img.setRGB(10,15,0x01020304);   // a=1 r=2 g=3 b=4
            WritableRaster r=img.getRaster();
            DataBuffer db=r.getDataBuffer();
            if (db.getDataType() != DataBuffer.TYPE_INT)
                throw new IllegalStateException("Hey that must be a int!");
            if (db.getNumBanks() != 1)
                throw new IllegalStateException("Uh - Someone else got to do this job!");
            DataBufferInt dbi=(DataBufferInt)db;
            int[] data=dbi.getData();
            System.out.println(" Pixel (10,15) = "+Integer.toHexString(data[10+32*15]));
            // Test: No coy
            data[10+32*15]=0xaabbccdd;
            System.out.println(" Pixel (10,15) = "+Integer.toHexString(data[10+32*15]));As you see it works best if you can set the pixel format and if it only contains a single array of data (i.e. bank).

Ftp too slow: pharlap and linux ftp problem

Similar Messages

Maybe you are looking for