-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Image Processing Time #42
Comments
It should only take seconds in worst case. Just tried msn.com:
The whole thing took 7 seconds including 1 sec sleep. Image was processes in 2 seconds. Send me your logs. |
Thanks for taking a look! I just restarted my Win7 comp and had nothing else running besides WRP just in case something was bogging it down. First I did a google search, which took about a minute. Then clicked on the first link, msn, which took about 8 minutes.
|
I have noticed that sometimes this happens on a first run of WRP. Try to stop it with ctrl^c, restart and see what happens. Also I have not done any testing on Windows 7 specifically. Could you try to run it on some other OS and see if you get any different result? Also there is a new version that might make it better: |
Runs fast like in your logs in Debian64 installed on a Virtual Box VM! Still runs very slow in Win7, so there must be some issue with Win7. What is the difference between these test executables and the v3.0 on your release page? Thanks for your help, I can finally use the browsers on my old Mac! |
The difference is a fix for #41 which was causing high CPU utilization. I was hoping that it would help with Win7 issue. I will take a look at it separately but I can't make any promises in regards to Win7. |
I just tried this yesterday on Win7 to internet browse on an old Mac Performa. I was curious if it's normal for wrp to take minutes to process an image before it gets sent to the Mac? For example going to msn.com took minutes. Doing a google search seems to take around a minute. Anyways, great job on putting this together! Seems to be the only viable way that i've found to use the internet browsers on these old Macs.
The text was updated successfully, but these errors were encountered: