CS 4 5:39 min and pass. out off memory
CS6 1.47 min and Finished.
Actually it is a great difference in this comparison.
So Zorro.ai it's my job. This perfection is far more of its work for 2 hours in work with illustrtator. But thanks for the appreciation.:)
But what about my work when I test such as the Zorro effect is only slightly faster. The difference with this test does not translate into differences in actual working example of this Zorro.
This form can be drawing within the hour if not for different lags or two hour with with better attention to detail and dashes. Now you're so tired of fighting with the interface Illustrator that you just get yourself let go.
But I give CS 6 and scratch the second chance it something more serious, and then ultimately decide whether to wait for the CS7 or Corel.
OK.... just ran across major performance degradation in CS6. I was working on some logos and after about the last 3 hours, a noticable slowness became worse and worse until I shut Illustrator down and restarted it.
Memory leak? Clipboard problems?
PS. zooming, panning, etc. were most effected. Now with a new start of Illy, everything is fast as normal.
I'm finding the same exact problems with AI6. Starts out OK and over 2-3 hours zooming, panning, dragging, resizing...etc. all slow down to an intolerable level. Same drawings on AI5...no problems.
Memory leak or memory purging seems to be my first guess as well.
On a 12 Core Westmere w/20gb RAM. This is not good.
Interesting test Wade. You are right ,I managed to create it in CS6, although it took about a minute to save it. I couldn't create it in CS5.
CS6; so far so good!
Dual-Core Intel Xeon 2.66 GHz
Gaussian Blurring itself in Illustrator CS6 was re-tooled, so not only is CS6 working with 64-bit processor operations, it's also new code generating the gaussian blurred drop shadows.
Therefore, I think comparing CS5's to CS6's ability to apply drop shadows doesn't provide useful test results if wanting to compare CS5's and CS6's general performance, since CS6 would out-gun CS5 in the drop shadow department even if it wasn't 32-bit.
Is my convoluted way of communicating with other humans makign sense here?
. . .
In other words - using drop shadows alone to test 32-bit VS 64-bit performance can't be conclusive because there are differences between CS5's and CS6's drop shadow effect, beyond 32/64-bit.
And as I like Marcus. Synthetic shadow square test does not translate into my feelings at work. For example, test Zorro. The differences are minimal. Perhaps the fault configuration, a custom video? That is why I asked.
But it still is for me is not the main problem. I do not think I see improvement in working with Illustrator. With few exceptions this is creative work in Illustrtaor, instead of a jet cockpit, I feel I should take part in the Wipeout. Maybe my bitterness and a bit exaggerating, but I have the patience to trace the program. ;(.
Well you're just asking for a snarky reply, so here goes...
You may have heard(???) of a service called "Google Translate", and it is obvious that Mariusz does not speak English fluently and used it or similar to add his post.
While G-T is rather good these days with German, Italien, Spanish, and French, it does have it's problems still with smaller countries languages.
Also may I respectfully add, you don't help matters with your "what" spelled in Ghetto-Greek either... you intollerent ignorant buffoon.
I'm also seeing terrible performance in CS6. In CS5 / 5.5 I couldn't use Illustrator at all (crashed / ran out of memory).
I have a file 300 compound paths with solid color fill and no other effects or other stuff. Most paths are very small with 10-20 anchor points, 15 or so are large with around 200 anchor points.
Simple actions like locking a layer or changing the layer order take 45 seconds. Changing the fill color took just over a minute.
In CS5, since I couldn't use Illustrator at all, I just started using Photoshop. It was MUCH faster and 64 bit. I thought I'd try to use Illustrator again since it had all these performance improvements for large files, they even mentioned cartography specifically (this is a map).
Photoshop's only issue with vector layers (for my use) is it has become even worse for subtracting one vector shape from another. I get errors all the time. I figured I'd give Illustrator another chance. I can't believe how slow it is.
System: Windows 7 x64, i7 3GHz, 24GB ram.
Everything I do in Illustrator uses almost no system resources. If it were simply an issue of being a large file and needing a beefy computer to handle it all, then I'd see my processor and/or ram getting hammered. But that's just not the case. I'm sitting at 6.4 GB RAM used and never go over 13% (about half of one core) CPU usage no matter what I do.
Photoshop has no issues at all with manipulating the vector shapes except the vector shape combining error. I'll just deal with that I guess and go back to PS.
So, here I am with one software designed for vectors that is super slow, and another that's much faster but has errors all the time on a simple operation.
I am also running Illustrator on Mac as well as Win machines but I have not seen this problem happening with me till now. But I think we should not assume that it is a generic bug and consider that not all users are observing this. I think we should try to provide some more information so that if people from Adobe looks into this post then they should clearly get to know the precise problem. So let us do one thing, if we are facing this issue we should share the following details:
1. Screen recording of the problem(if possible).
2. How is Illustrator behaving after quitting daemon(user) processes or startup processes(if any).
3. Screen resolution(please check if changing the screen resolution helps solve the problem).
4. Any other information that we feel can be helpful.
I also noted that the perfomance on my machine (MacPro SSD, 12gb Ram, 8 core, QuadroFX 5600) is sluggish, quite the diference between CS5. I only hope Adobe gets his hands on this and fix it. Meanwhile I'm returning to CS5
Read this and maybe the personal account cache might help.
I have an Original MacPro and lost 8 of my 16 GB of RAm temporarily but AI CS 6 is faster and more responsive than CS 5 any day.
I get back the my other 8 GBs of Memory and I bet it flies.
I say you have a font cache problem that CS 5 is not seeing.
The Zorro file is not Fast in CS 6 but it is faster than CS 5 and requires much less redraw.
And don't worry guys yiu are right I will not be revisiting this thread.
Same here. I always found Illustrator a bit sluggish on the Mac compared to Windows but this version is worse. Screen-redraw panning and moving around object is even slower than before. I found out that this 'sluggishness' is also related to how OSX redraws. I use OSX's Quartzsimple utility to disable beam sync which really improved performance in this respect in CS4. Unfortunately it doesn't make as big of a difference in CS6 but it's a bit faster. You might want to give that a try.
Macbook Pro 5.5 / Mac OS 10.6.8 / 8GB Ram
My experience so far has been that the problem is progressive. Starts out OK and over time it slows to a crawl. Particularly on my large scale industrial design stuff. This really leads me to think this not a Mac redraw issue but rather some sort of memory leak/buffer purging problem. I don't have this issue with CS5.
First rule of beta: "If something failed that used to work, what changed?" To me, this is a classic example of shoving something out the door half baked because of an arbitrary suite release deadline. All the Adobe fiefdoms had to hit the mark ready or not. Some succeeded, some didn't. I'd park AI in the "didn't" category. The thing feels like a beta. And as far as I'm concerned, not ready for prime time.
I've turned back to AI CS5 to get actual real world work done efficiently. I'll wait and see what they come up with for an incremental update.
I have taken the time to use and get to know it a little better after my initial critique. I have found that I have significantly adapted my way of working to accomodate AI CS6 and all its shortfalls. There are many things that i now instinctively avoid doing. I am now avoiding the following troublemakers:
external file linking (embed everything and keep memory clear)
effects (using blends and appearances to emulate effects)
gradient appearances (especially gradient stroke)
multi artboards (split into smaller documents)
using spotify with AI (or any streaming for that matter)
using fonts (i now convert to outlines immediately)
symbols (stopped using completely)
hand tool (i use the artboard/navigator palette with zoom controls)
in doing this, i can get by with AI CS6 but it really is the type of experieince i would associate with a piece of opensource software. I am also finding other ways to achieve what i want in other ways but they feel hacky and dont deliver the same end results.
very unhappy atm.
Ai CS6 is working very well for me. I have been using it now intensively for a few weeks. I have noticed I seem to be able to work quicker on larger files
typically 50 - 60 MB than previously. I have used ,amoungst others, inner and outer glows, gradients, symbols, fonts, trace tools,saving - all seem quicker than CS5.
Not so keen on the lack of sliders in effects panel.
MacPro1,1 Dual-Core Intel Xeon 2.66 GHz 9 GB
I have observed that we are distributed on this post with some people facing the issue and many are not. This makes me believe that those having problems have something different from the others not having the problem. This difference can be in the screen resolution(which I asked for in my last post) or monitor set up or may be in the kind of work that you do. Based on my long experience with illustrator, I can see some of the possible areas of difference causing the problem. These are:
Discussing issues on the forum would give fruitful results only if we provide some constructive feedback and asked information so that others can help.
Also, I would like to mention that whenever I come across such a problem, I prefer reporting it as a bug @ https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform. You may also use the same approach.
After reading your post I decided to close all the panels and start working on a design that was presenting low performance and it does improve. Later I opened the same design but this time with all the panels open and once again it was very slow. It's usable now but I would like I didn't had to do this in order to Illustrator work properly.
you may not have to close out all the panels. with some hit and trial you should be able to isolate the panel that is causing trouble to you and then ask the forum if others are seeing it too. As lot of other users on the thread I am not facing any performance issues.
O that is a good sign to catch the culprit. I suspect that it can be Layers Panel, any of the Type panels, Image trace, appearance or swatches panel. It would be great if you could isolate the specific panel. I hope we are very near to finding the exact problem.
Closing the layers panel makes a significant difference to me and practically remedies the problems ive been having. Its certainly nice to see illustrator working smoothly again but sadly i need the layer panel open. Almost there : )
It makes me happy that a constructive communication has helped us find the cause of the problem. But it would be great if others folks who were facing the problem validate it. In the mean time, a bug can be reported to let Adobe know of the problem.
Hiding all the panels doesn't improve performance for me.
My normal secondary monitor size is 1680x1050 and at fullscreen its pretty laggy even with no panels visible (tab key).
The only thing I"ve found to work is making the canvas viewport about one quarter size. and performance is normal and comparable to CS5 full screen. But obviously that is too small an area to be comfortable.
Could you guys post your screen sizes?
On a Mac my display is 1920 x 1200 and CS 6 clearly out performs CS 5
Have you read about dumping the personal cache files that might change things, you can reade about it here.
Is it that when you work in full screen mode, other panels are open in the background but are not visible. Can you verify by collpasing or closing the panels. Also, I have been asking about Screen resolution. I also think monitor size and resolution can play a role in it.
I've narrowed my constant crashing down to the navigator not updating quickly enough when i zoom in and out. If i grab the navigator red cube and its not updated correctly....crash. Have closed it (although i am finding it hard to adjust workflow without it) and i so far have not had a crash.
screen res 1680x1050
ATI Radeon HD 5870/1024VRAM driving dual monitors: 23" ACD-1920 x 1200, 30" ACD-2560 x 1600. The 23" holds all the palettes and the 30" is the work area.
I've been reading the various suggestions to shut down the palettes or turn off thumbnails in Layers. Sorry, but that's simply unacceptable. Particularly thumbnails, It's like driving with your windshield painted black. I need to see that stuff. Constantly going to the Layers options to turn it on and off is real work flow kill.
I can work on my large industrial designfile in PS5 all day and not have issues. Running the same workspace(s) in PS6, the slowdown becomes an issue. Again, I'd like to point out that a session doesn't start out slow immediately. It progresses over time....suggesting some sort of buffer problem or memory leak.
If it turns out that it's how PS6 now deals with dual monitors and/or palette population, I expect Adobe to deal with it and improve the performance to at least where it was in CS5. Can't wait to see what the next revision brings.
Judging by the amount of reads this subject is getting, I'd say it is a concern to more users than those contributing to this thread.
Can you guys check if you have Application Frame on? (Window > Application Frame) Its off by default but I've always been using it on and think it causes a redraw performance drop. Try it off.
Application frame doesn't make a huge difference after all IMO.
Ai's not using the GPU to redraw and a 2.0ghz i7 is not enough mac juice to handle the new engine.
Panning around PS6 uses 7% CPU and is smooth as butter where its 70% in AI6 and painful to use.
Our diagnosis efforts are not really getting anywhere.
Can we get some official responses from Adobe on if there are any plans to look at this, please?
For me it does drop performance, it's annoying having to work with a crippled Illustrator.
I know this is not the thread but Bridge CS6 keeps crashing and crashing, this CS6 release is not what I hoped for.
You clearly have a cache problem and or a permissions problem and why you are not reading the article I posted I do not understand it will offer you the remedy you need but you have to read it and yes you have to do some work and if you do this it will bhe fine.
I dumped my cache because I lost some performance which I had initially gain with CS 6 but once I repared the permissions and dumped the personal cahe files all was back to normal and now that I got my additional 8 GB of memory back so that I now have 17 GBs things are working really well.
Here is the article it is long but offers you the answers you need so you need to read and I think if you don't read it you should stop complaining because it is your own fault zI have yet to see the Bridge crash in CS 6 thought once in a while CS 5 has so this is definitely your problem.
BTW the application frame or the number of opened panels has no effect on performance here, but then I dumped the personal cache files.
Actually I read the instructions for fixing this the first time you post them. And I followed them and did the work it required, in fact I installed Illustrator in other computer and fails also. For me it's not so clear even following the post. So that's why I'm still complaining.
From the discussion so far, it appears that any one of the following is causing a problem:
1. Font cache(Try clearing font cache)
2. Layers Panel (Try to work by keeping it closed)
3. Screen Resolution (Try to work by changing the screen resolution or working in single monitor)
The intention here is that you should be able to find the cause of the problem and not change the way you work. But trying the above things is important because if we succeed to find the exact cause, then getting the solution would be easy as we can report it to Adobe then. I am not sure if discussions like this forces Adobe to fix the problems. It needs to be reported as Bug.
Europe, Middle East and Africa