E7-00 performance issue: screen context switch cau...

I've already tried reinstalling the firmware, and am considering a hard reset but want to determine how this happened first. The E7 is a dev phone, I'm more interested in determining how the issue arose and preventing it than I am in fixing it.
I received the phone yesterday. I started it up without a SIM card in place and tried to connecty with Ovi Sync to get my contacts onto it. Ovi Sync was bogging down the mobile, and never seemed to complete (ran for hours) across several reboots, so I removed that account. This was the only 'glitch' I observed prior to the subject of this post.
At this point, the device boots reasonalby fast, and Ovi Sync has succesfully sync'd my contacts, calendar, notes, etc. I've setup a single gmail account as well. Aside from that it is pretty much pristine.
The primary symptom is as described in the subject: any event that changes the screen context causes the device to be non-responsive for 5-10 seconds. seconds. this is a very long time. Press the menu button one, wait 5 seconds, touch 'Applications' and wait 5 seconds more, etc etc. I even get a second or two of delay when swiping between homescreens (not just the normal delay, but several seconds where I hve time to try pressing 'Call' and can wait long enough to observe that this touch event didn't do anything).
Once an app is running it seems to run just fine.
any thoughts?
N95-1 ---> N97-NAM ---> N900 ---> E7-00 + N900 (I use them both)
(N95 was pretty good, N97 had potential but utterly failed to deliver, N900 is absurdly good. Those of you wondering, "should I try N900/Maemo/MeeGo"? The answer is a resounding YES)
Solved!
Go to Solution.

You could try rebooting the phone, and also turn off theme effects, my E7 has none of the delays you seem to be having, and part of the problem may be the attempt to sync with no sim. If it continues and you haven't put too much data on it , it may be worth trying tto restore factory settings, and re-stync your contacts and set up your goohle account again ?
If that doesn't work you may need to visit a care centre
Also did you check updates, there was a minor update a couple of days ago which increased performance and had some bug fixes, it may help.
Good Luck
If I have helped at all, a click on the White Star is always appreciated :
you can also help others by marking 'accept as solution'

Similar Messages

Performance Issues - Screen Redraw etc.?

I have a new MacBook Pro 15" (8GbRAM, 2 GHz i7) Using 30" Cinema Display, OS 10.7.2. I'm using Photoshop CS 5.1 (12.1 x64) Extended. After working for awhile I get performance lag -mostly drawing, cloning etc. Then the cursor starts behaving unpredictably -usually drawing slightly BELOW where the crosshairs are. Then the screen refreshes slows and the screen redraw occurs in very large blocks -VERY slowly. Reloading PShop doesn't help, but rebooting the laptop does solve the problem -until it happens again. In an earlier post I was advised that PShop CS4 was the cause (not compatible w/Lion). But I now have the latest version of Photoshop (my primary application).
- In this situation, I would suspect corrupted PShop Prefs, but I don't think that's the case, as reboot solves the problem. It was also the exact same issue when I ran CS4.
- Could this be an issue wuth using the 15" Macbook Pro with a 30" display? I was also advised that I could NOT upgrade the video card (soldered to motherboard) but this is not a MacBook Air.
- RAM issue? I did upgrade to 8Gb -but I purchased quality RAM from a reputable dealer. I have had no crashes or other issues (other than the Photoshop issue. I will test the RAM.
- Any know CS5 issues/bugs in this area?
Thanks

I think you're seeing more of the 1.7 video driver bugs. The cursor offset is a known one, along with some "cursor doesn't draw correctly" bugs.
You can try turning off OpenGL drawing in preferences to avoid many of the problems (don't know if that'll fix the cursor or not).
But the real fixes need to come from Apple fixing their display drivers.

Performance issue with context search

We have a performance problem with a table tise with about 10 mio rows
and a text column tise_desc with short descriptions (about 300 characters per row).
We currently use mixed queries of the form (here very simple)
SELECT /*+ FIRST_ROWS(10) */ * FROM tise
WHERE reg_id = 'REGI0000000000000132'
AND contains(tise_desc, '(employment)' ) > 0
When the structured query part (here reg_id) and the fulltext part (contains) is not selective some queries take about 30 sec to 90 sec to process.
When we repeat the query it only takes about 1-3 sec (may be due to caching).
We are not interested in scoring nor in sorting the data.
Until now we have tried to use different hints, use different index types (btree versus bitmap), use different sql query syntax, use one fulltext index with xml and within syntax without any real progress.
Has any body addtional ideas?

Since you are doing a combination of structured queries and simple text queries on only one column, a ctxcat index with a catsearch may be better than a context index with a contains search. The catsearch has fewer additional features available than contains, but some context features can be done with catsearch through a query template. If you only do simple searches and don't need those extra features then it doesn't matter.
Make sure you have current statistics, so that the optimizer can use them to select the best execution plan.
Use bind variables instead of literal values in your searches. When you use bind variables, the previous query in the SGA can be reused for different variable values without reparsing, so that every query with new values has the same effect as rerunning the previous query. This alone could account for the different between 30 to 90 seconds on the first run and 1-3 seconds on the second run.
If you are not using scoring or sorting, then you might be better off without the first_rows hint, which chooses the best path for sorting. Try it both ways and see which works best for you.
Once you have tested with a ctxcat index, current statistics, and bind variables, if it is still slow you may be able to use some tracing to determine the cause of the slowness and adjust some memory settings or some such thing. You can find more tuning hints for Oracle Text here:
http://download.oracle.com/docs/cd/B28359_01/text.111/b28303/aoptim.htm#i1007227
Please see the demonstration below that implements the recommendations above.
SCOTT@orcl_11g> CREATE TABLE tise
2    (reg_id        VARCHAR2 (20),
3      tise_desc VARCHAR2 (300))
4 /
Table created.
SCOTT@orcl_11g> INSERT INTO tise VALUES ('REGI0000000000000132', 'employment')
2 /
1 row created.
SCOTT@orcl_11g> INSERT INTO tise SELECT object_id, object_name FROM all_objects
2 /
68770 rows created.
SCOTT@orcl_11g> -- try a ctxcat index instead of a context index
SCOTT@orcl_11g> -- (make sure the index is not fragmented by periodically
SCOTT@orcl_11g> -- dropping and recreating or altering and rebuilding or optimizing)
SCOTT@orcl_11g> BEGIN
2    CTX_DDL.CREATE_INDEX_SET ('tise_iset');
3    CTX_DDL.ADD_INDEX ('tise_iset', 'reg_id');
4 END;
5 /
PL/SQL procedure successfully completed.
SCOTT@orcl_11g> CREATE INDEX tise_id_desc_idx ON tise (tise_desc)
2 INDEXTYPE IS CTXSYS.CTXCAT
3 PARAMETERS ('INDEX SET tise_iset')
4 /
Index created.
SCOTT@orcl_11g> -- make sure you have current statistics:
SCOTT@orcl_11g> EXEC DBMS_STATS.GATHER_TABLE_STATS (USER, 'TISE')
PL/SQL procedure successfully completed.
SCOTT@orcl_11g> -- use bind variables so that the query in the sga can be reused
SCOTT@orcl_11g> -- for different variable values without reparsing:
SCOTT@orcl_11g> VARIABLE search_reg_id VARCHAR2 (20)
SCOTT@orcl_11g> VARIABLE search_desc VARCHAR2 (2000)
SCOTT@orcl_11g> EXEC :search_reg_id := 'REGI0000000000000132'
PL/SQL procedure successfully completed.
SCOTT@orcl_11g> EXEC :search_desc := 'employment'
PL/SQL procedure successfully completed.
SCOTT@orcl_11g> -- query using catsearch with a ctxcat index and bind variables:
SCOTT@orcl_11g> COLUMN tise_desc FORMAT A30 WORD_WRAPPED
SCOTT@orcl_11g> SET AUTOTRACE ON EXPLAIN
SCOTT@orcl_11g> SELECT *
2 FROM   tise
3 WHERE CATSEARCH (tise_desc, :search_desc, 'reg_id=''' || :search_reg_id || '''') > 0
4 /
REG_ID               TISE_DESC
REGI0000000000000132 employment
Execution Plan
Plan hash value: 409728589
| Id | Operation                   | Name             | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT            |                  | 3439 |   100K|   102   (0)| 00:00:02 |
|   1 | TABLE ACCESS BY INDEX ROWID| TISE             | 3439 |   100K|   102   (0)| 00:00:02 |
|* 2 |   DOMAIN INDEX              | TISE_ID_DESC_IDX |       |       |            |          |
Predicate Information (identified by operation id):
   2 - access("CTXSYS"."CATSEARCH"("TISE_DESC",:SEARCH_DESC,'reg_id='''||:SEARCH_REG_ID|
              |'''')>0)
SCOTT@orcl_11g> SET AUTOTRACE OFF
SCOTT@orcl_11g>

NW 2004s BI: performance issue on context menu in web application

Hi BI-Gurus,
Currently I am looking for a possibility to speed up the context menu within a web application.
Therefore, queries have been created that should be accessible via BEx Analyzer and Enterprise Portal. In BEx Analyzer context menu of measures and characteristics appears quickly after right-clicking. However, it takes up to 12 sec to display the context menu in the corresponding web application for the initial call. The 2nd, 3rd,... call of the context menu is about two or three times quicker .
Is there anybody out there who knows which parameters affect the call of the context menu in a web app and how to speed up in this case? Please note that I am working on a NW 2004s BI system with SPS12 installed.
Thanks for your feedback.
Regards
Sascha

NW04s Web Context Menu is slower than the 3.X, but it does not take 12 secs for me, more like 2-3 secs. Try deleting your browser cache and running the template again and see whether that makes any difference.
The rendering is done on the front end side when the template is loaded all the required JS files are also downloaded (around 12 different JS files), depending on what other applications you have open that also will affect the time taken for this.
Thanks.

Performance Issue with Selection Screen Values

Hi,
I am facing a performance issue(seems like a performance issue ) in my project.
I have a query with some RKFs and sales area in filters (single value variable which is optional).
Query is by default restricted by current month.
The Cube on which the query operates has around 400,000 records for a month.
The Cube gets loaded every three hours
When I run the query with no filters I get the output within 10~15 secs.
The issue I am facing is that, when I enter a sales area in my selection screen the query gets stuck in the data selection step. In fact we are facing the same problem if we use one or two other characteristics in our selection screen
We have aggregates/indexes etc on our cube.
Has any one faced a similar situation?
Does any one have any comments on this ?
Your help will be appreciated. Thanks

Hi A R,
Goto RSRT--> Give ur query anme --> Execute =Debug
--> No a pop up ill come with many check boxes select "Display Aggregates found" option --> now give ur
selections in variable screen > first it will give the already existing aggregate names> continue> now after displaying all the aggregates it will display the list of objects realted to cube wise> try to copy these objects into notepad> again go with ur drill downs now u'll get the already existing aggregates for this drill down-> it will display the list of objects> copy them to notepad> now sort all the objects related to one cube by deleting duplicate objects in the note pad>goto that Infocube> context>maintain aggregates> create aggregate on the objects u copied into note pad.
now try to execyte the report... it should work properly with out delays for those selections.
I hope it helps you...
Regards,
Ramki.

Macbook screen cracked, HD and performance issues

I am definitely disappointed with my computer.
I have a Macbook 13.3" 2.4Ghz Intel Core 2 Duo 4Gb 160Gb HD, Serial#: W8**VM0P5, and within 1,5 year I have faced many issues, which are related here:
September 24th, 2008
O.S. CRASHES
I bought it in late September 2008, in Cologne, Germany, at the reseller "Compustore PC Gmbh", and also asked 4Gb Ram, and a Wireless mighty mouse.
After changing the Ram memory, i went home; and a few days later, the problems came. Sometimes, the system crashed suddenly, showing the grey screen: "You must restart your computer". I thought it was normal, and continued to use, when it became more frequently (Picture: http://picasaweb.google.com/gstorck/MacbookProblems#5476986272817173138). It was little strange for a new laptop, and then I took it back to the store to fix it. The seller just took a look, changed some configurations, and gave me back again. I did this twice, and had to get back to the store for the third time, due to new crashes and some lack of performance. Then the seller replaced the Ram memory, with new 4Gb.
After that, the system worked more stable; the problem happened some two or three times after some months, but it was ok.
November 9th, 2009
HD Problems
One year later, in late 2009, I purchased a Mac OS update, the Snow Leopard. I was back to Brazil, where I live till today. During the OS installation, something went wrong and it couldn't be completed. Mac asked me to restart the computer, but then the system didn't start anymore; some files were corrupted. I guess there was not enough space to install the update, so it was not completed; but it should be no reason to the corruption of the OS.
November 10th, 2009
I took my computer to the local Apple technical support, the "Omni Informatica", in Curitiba, PR, Brazil, to format the HD and reinstall the Snow Leopard. As I needed more space, I also changed my original 160Gb HD for a new 250Gb Western Digital HD. The service was finished in Nov 17th.
I noticed also little cracks in the laptop case, but I had no time to insist with the bad local technical support to repair it (I know Apple already acknowledged this problem.) They said, at first, that they would have to ask the Apple USA to send the body, or something like that.
(Pictures:http://picasaweb.google.com/gstorck/MacbookProblems#5476986477312032226)
January 12th, 2010.
SCREEN CRACKED
The reinstallation was ok, and the laptop was running well. Suddenly, when I take the Macbook from the case and open it on my desk, something pretty wrong appears: a large crack on the lower right corner of the screen.
It was not dropped, it was not crashed, and I did not "close it with a pen inside".
The screen simply cracked. And as so many similar problems with another users I could easily find on the web, I really expect Apple to admit it as a Manufacture's fault. The local technical support said it is no other thing except I hit the laptop, or dropped it, so it's all my fault. (See Picture 3)
The only thing they can offer me is to repair the screen for R$1200. I am definitely not going to pay for this; a "normal" and good pc laptop costs this price (And a new basic macbook costs today R$2400).
If the problems were just it, it would be not so bad.
(Pictures: http://picasaweb.google.com/gstorck/MacbookProblems#5476986361400585122)
February 11th, 2010
HD FAILURE
After 1 month, on Feb 11th, my new 250Gb HD simply stopped working. Different from the first time, that the HD was just corrupted, this time it has really broken, it died. I had it all backed up, but I have lost the HD.
Back again to the technical assistance, they said to me the problem was the same that cracked my screen: my fault, on letting the laptop fall, or hitting it with some kind of pressure. They couldn't do anything, and even the Western Digital 3-month Warranty would not cover this type of problem ("user's misuse").
May 28th, 2010
DECREASE IN PERFORMANCE
I'm working again with the original 160Gb HD (formatted and reinstalled), and some other external drives to store my files.
It's been quite difficult to deal with all this Data and Screen problems, and now the Macbook's performance is decreasing every day. It's been slower to process operations and to launch the applications. Sometimes, the system does not even sleep anymore when the laptop is closed, or it takes so long time to sleep that it just sleeps when I open it again. Besides, sometimes the mouse pointer disappear, and some bizarre graphics take its place.
Don't forget: It's a 1,5-year-old Macbook, with 2.4GHz, 4Gb RAM and the O.S. is installed for no longer than 4 months. It is supposed to work better, I guess.
I saved a lot of money to buy a good computer, and to get rid of the endless issues I had with PCs. That issues never were so serious with the ones I face now with Macbook.
Even if I pay R$1200 to replace the screen, with the money I don't have, I would still stand these performance issues, which seem to have come with this problematical laptop. I hope to have some solution from Apple, if it want to deliver what it promises and want to keep a customer.
Otherwise, I will have to change to another system platform and another computer manufacturer, to see if I stop throwing money away with these devices. I think that maybe at least, the cost-benefit ratio will be higher.
Did anybody receive contact from Apple support about these screen problems?
Guilherme R. Storck
Apple user since 2008
<Edited By Host>
gstorck (at) gmail (dot) com

Well, your first issue is pretty clearly just some bad RAM, and it sounds like even the replacement RAM was bad. Who knows if the people who put it in had any kind of clue what they were doing. I've seen repair shops where people are smoking in the same room they do repairs.
Second problem sounds typical of a failing HDD. It's a fairly common problem with laptops... Apple, Dell, Lenovo, HP, Acer... Probably the single most common problem with laptops no matter who makes them. People get this notion in their heads that the "portable" aspect of laptops means you can pick them up and carry them all over while turned on. Which you can... If you don't mind dramatically shortening the life of the HDD. What "portable" REALLY means with laptops, is that they are easy to move if you put them into a powered down state. They should NEVER be moved around when in normal operation. And since you seem to do a bit of traveling, if you're on a plan, and there's turbulence, you should shut the laptop off until it smooths out.
The screen cracking could have something to do with the rather sudden change in climate. Germany isn't exactly the frozen tundra, but it is a pretty different climate from Brazil, and changes in things like humidity could cause problems. The laws of thermodynamics tell us that things expand as they heat up, so if there's already a crack somewhere, it could easily get worse as a result of increased heat.
And since your initial hard drive was already starting to fail, it hasn't magically stopped failing since being removed from the system, so obviously performance is going to get worse.
At this point, it's pretty much impossible to tell where the damage was done, so you're probably just out of luck. The people in Germany could have screwed something up, or the people in Brazil, it could have been environmental damage, and it's possible the defect was always there, it just didn't manifest until recently. There's just no way to tell for sure. So Apple is unlikely to do anything for you.

Performance Issue : Why does ADF Taskflow Portlet (JSF bridge portlet) loading ADF Specific images, css, js everytime from portlet producer with dynamic URL with portlet_id and context parameters?

Hi All,
We have used WSRP Portlet in Webcenter Portal Page. The Portlet is created using JSF Bridge out of ADF Bounded Taskflow.
It is causing Performance issue. Every time static content like js, css and images URLs are downloaded and the URL contain portlet_id and few other dynamic parameters like resource_id, client_id etc.
We are not able to cache these static content as these contains dynamic URL. This ADF Specific images, js and css files are taking longer time to load.
Sample URL:
/<PORTAL_CONTEXT>/resourceproxy/~.clientId~3D-1~26resourceId~3Dresource-url~25253Dhttp~2525253A~2525252F~2525252F<10.*.*.*>~2525253A7020~2525252FportletProdApp~2525252Fafr~2525252Fring_60.gif~26locale~3Den~26checksum~3D3e839bc581d5ce6858c88e7cb3f17d073c0091c7/ring_60.gif
/<PORTAL_CONTEXT>/resourceproxy/~.clientId~3D-1~26resourceId~3Dresource-url~25253Dhttp~2525253A~2525252F~2525252F<10.*.*.*>~2525253A7020~2525252FportletProdApp~2525252Fafr~2525252Fpartition~2525252Fie~2525252Fn~2525252Fdefault~2525252Fopt~2525252Fimagelink-11.1.1.7.0-4251.js~26locale~3Den~26checksum~3Dd00da30a6bfc40b22f7be6d92d5400d107c41d12/imagelink-11.1.1.7.0-4251.js
Technologies Used:
Webcenter Portal PS6
Jdeveloper 11.1.1.7
Please suggest , how this performance issue can be resolved?
Thanks.
Regards,
Digesh

Strange...
I can't reproduce this because i have issues with creating portlets... If i can solve this issue i will do some testing and see if i can reproduce the issue...
Can you create a new producer with a single portlet that uses a simple taskflow and see if that works?
Are you also using business components in the taskflows or something? You can try removing some parts of the taskflow and test if it works so you can identify the component(s) that causes the issues.

MacBook Pro performance issues w/2nd monitor and FCP7

I have this MacBook Pro bought brand-new in January 2010:
Model Name: MacBook Pro
Model Identifier: MacBookPro5,2
Processor Name: Intel Core 2 Duo
Processor Speed: 3.06 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 6 MB
Memory: 8 GB
Bus Speed: 1.07 GHz
and until today had never attached a second monitor to it. Today I hooked up my Samsung 24" to do some dual screen editing in Final Cut 7.0.3. I was unable to play back my video at full speed in the second monitor, and after a few seconds of skippy playback I'd get that error message about unable to play back video at full speed and to check my RT settings. I was using a Mini DisplayPort to DVI adapter. My computer has no issues playing the video in the laptop's monitor at any resolution and any quality settings (I've never changed the RT settings or anything else in the menu ever but I tried every combination this time). I then tried using my TV as a 2nd monitor with an HDMI adapter. Same performance issues. I then tried my friend's newer 13" MBP 8,1 and it performed flawlessly with the same project & footage. I feel like my $3,000 computer should outperform a $1,200 one even if mine is a year and a half older. Any advice?
Chris

Wow, you posted this perfectly to coincide with an identical problem, albeit using Logic Pro 9.1.5 rather than FCP.
Last week, I purchased a 23" external monitor to use alongside my "flagship" 2011 15" hi-res, 2.3 i7 Macbook Pro with 8Gb of RAM.
It is connected via a mini-DVI to D-sub analog (not that that should matter?) and all appeared fine.
The first issue I had was with my MBP's fan now running CONSTANTLY, when I have the second monitor attached. Even when the machine is completely idle.
When using the machine to record audio, this is a fairly hefty problem and not something I had anticipated - indeed why would I anticipate such a thing?
What is far, far worse though is that over the last few days I have had repeated problems with performance drop-outs and errors in Logic and I have trying to fathom out why. Realising that the only major system change made, was the above monitor connection, I ran some tests.
I restarted my MBP, no other apps were running and with my new 23" monitor attached acting as main display with MBP built in display on as secondary
I loaded up a fairly demanding Logic project which was hitting 40% to 60% CPU usage when using the built in MBP display last week
I ran activity monitor and had CPU usage history open
The above project now repeatedly overloads and playback halts in a given 8 bar section - with CPU at 80% most of the time
I disconnected the external display, no shut down, I just let the machine switch to the built in 15".
Started the same project, the same 8 bar section and hey presto - CPU usage back down to 40% to 60%
The above was reflected in the CPU usage history with the graph showing CPU use down by about a half, when running this Logic project WITHOUT the external display.
There is a very useful benchmark Logic project that has been used as a test by many users to gauge Logic performance on given Apple hardware.
The project has about 100 tracks pre-configured with CPU intensive plugins, designed to tax the CPU.
The idea is that you load up the project with tracks muted, press play and then unmute the tracks steadily until Logic us unable to play contiunously because of a system performance error.
On my MBP, with the external monitor NOT attached, I can play back around 50 of the audio tracks in this benchmark project.
With the monitor attached, I can get about 22 tracks playing.... which is actually a far worse a performance drop (-50% I think!?) than with the first example!
I did also try with just the external monitor attached and not the MBP display and performance was about 10% better than with dual monitors - so still extremely poor, to say the least.
This machine is the flagship MBP and has a dedicated AMD Radeon HD6750 GPU which should take care of most if not ALL graphics processing - I mean it's capable of running some pretty demanding games!
Putting aside the issue of constant fan noise, there is no reason AT ALL, why using an external monitor should tax the i7 CPU this way - it's not as though Logic is graphically demanding... far from it.
I am on 10.6.8, Logic 9.1.5, all apps up to date via "Software Update".
I will of course, be contacting Apple...

How should I report forum performance issues?

The forums rely heavily on the caching features of browsers to improve the speed of page rendering. Performance of these forums should greatly improve after a few pages because more and more of the images, css and javascript is cached in the browser. As a consequence, when reporting forums performance issues the report should include some information on the state of the browser cache to determine whether the issue is a browser issue or a server issue. Such detailed information is generally not available from just watching the browser screen, but needs to come from specialized tools such as performance monitor plugins and recording proxies.
The preferred report method for performance issues is to use the speed reporting features build into or available as a plugin for a browser for both the page you want to report a problem with and several refence pages in the site. Detailed instructions are listed below separated out for different browsers. If possible, please use Firefox for submitting the report because it provides an export format that can be read back electronically.
Known performance issues
The performance issues with any screen with a Rich Text Editor, such as the Reply window and the compose Private Message window have been acknowleged and improvements are being implemented.
Mozilla Firefox (preferred)
Warning: it is currently not recommended to generate a speed report when logged in. The speed report has enough detail for somebody else to hijack your session and impersonate you on the forums. If you really must report while logged in, make sure you log out your browser after generating the speed report and wait at least 4 hours before posting.
Install the Firebug plugin
Install the NetExport 0.6 extension for Firebug
Enable all Firebug panels
Switch to the "Net" panel in Firebug
Click on this link
Export the data from the Firebug Net panel
Click on this link
Export the data from the Firebug Net panel
Browse to the page where you are experiencing the performance problem.
Export the data from the Firebug Net panel
Click on this link
Export the data from the Firebug Net panel
Click on this link
Export the data from the Firebug Net panel
Browse to the page where you are experiencing the performance problem.
Export the data from the Firebug Net panel
When you report a performance problem please attach the 6 exports from the Firebug Net panel and an explanation of how you are experiencing the issues (for instance how much slower it is then normal) and include a description of your internet connection (dial-up, dsl, cable etc.) and the country from where you are connecting. If you have non-standard tweaks to your Firefox configuration (such as pipelining enabled) or are running any plugins please include that information in your report as well.
Google Chrome
Open the Developer Tools (Ctrl-Shift-J)
Navigate to the resources tab
Enable resource tracking.
Click on this link
Export the resource loading data.
Reset the data by disabling and enabling resource tracking
Click on this link
Export the data
Reset the data by disabling and enabling resource tracking
Navigate to the page where you experience the performance problem
Export the data
Reset the data by disabling and enabling resource tracking
Click on this link
Export the data
Reset the data by disabling and enabling resource tracking
Click on this link
Export the data
Reset the data by disabling and enabling resource tracking
Navigate to the page where you experience the performance problem
Export the data
Since Google Chrome does not have an export format for the Resource Tracking information best current practice is to take a screenshot and note the hover details for any resource with a tail that is longer then 25% of the total load time. When you report a performance problem please attach the screenshots and an explanation of how you are experiencing the issues (for instance how much slower it is then normal) and include a description of your internet connection (dial-up, dsl, cable etc.) and the country from where you are connecting.
Apple Safari
The Apple Safari Web Inspector has a Resources panel similar to the Resources panel in the Google Chrome developer tools.To get there, follow these steps:
Show the menu bar.
Go to preferences
Go to the Advanced Tab
Check “Show Develop menu in menu bar”.
From the Develop menu select “Show Web Inspector”.
Collecting the performance information and exporting works exactly the same as in Google Chrome. Please refer to the instructions for Google Chrome.
Microsoft Internet Explorer
IE does not have native features to analyze web traffic. No plugins have been found that produce the required information (please let us know if we missed any). For now, please reproduce the issue with Firefox, Chrome or Safari.
Please note that due to the reliance on Javascript for the interactive effects the performance of these forums will be much better on MS IE 8 then on previous versions of MS IE.

Hi
It works, check once again...
regards
Swami

Serious performance issue with LV 7.1 Development Environment

I'm posting this issue to the forums prior to submitting a bug report to ensure that the problems I'm having are reproducible. To reproduce this bug, you're going to have to be an advanced user with a large project (hundreds to thousands of VIs) as the performance problem is related to the number of VIs loaded.
The issue is the increasingly poor performance of the LabVIEW 7.1 Development Environment as the number of VIs in memory increases. The actions affected include switching between front panel and diagram, saving a VI, copy and paste, clicking a menu, and the mysterious time spent (compiling? editing the runtime menu? changing the toolbar state?) between pressing the run button and when the code actually starts executing. Scrolling and, interestingly, copying via a control-drag are not affected. Running time of entirely on-diagram code does not seem to be affected.
These problems are quite severe and significantly decrease my productivity as a programmer. Since they are development environment UI issues, it's been difficult for me to find a good example VI; the best I can do is the attached "LV Speed Test.vi". It doesn't test the issues that affect me most, but it seems to suffer from the same problem.
This simple VI just shows and hides the menu bar 100 times in a tight for loop. When it is the only VI loaded, it executes in about 350 msec on my machine. (2.4 GHz P-IV/640 MB RAM/Win2k). However, when I load a single project-encompassing VI (let's call it the "giant") that references a total of about 900 user and VI-lib subVIs, the test routine takes almost a minute and half to run...about 240 times slower! I've tried this on my laptop with similar results.
The problem appears to be related to the *number* of VIs loaded and not the memory utilization. For example, if I close the "giant", and create a new VI ("memhog") that does nothing but initialize a length 20,000,000 array of doubles and stores it in an uninitialized shift register, LabView's overall memory usage (as shown in the task manager) jumps enormously, but LV Speed Test executes in about 450 msec...only slightly slower than with a fresh copy of Labview.
The problem seems to be related to excessive context switching. The Windows task manager shows over a thirteen hundred page faults occur when "LV Speed Test" is run with the "giant" in the background, versus zero or none when run by itself or when "memhog" has used up 160+MB of space.
The problem only seems to affect the frontmost window. (Unfortunately, that's where we LV programmers spend all of our time!) If you start "LV Speed Test" and then put "giant" in the foreground "LV Speed Test" runs much faster. In fact, if you use the VI server to put the "giant" VI in the foreground programmatically at the start of "LV Speed Test", execution time drops back to 450 msec, and there are no page faults!
These results show the issue is not related to video drivers or the Windows virtual memory system. My suspicion is that there is a faulty routine in LV 7.1 that is traversing the entire VI hierarchy every time certain events are thrown in the foreground window. It could be due to a problem with the Windows event tracking system, but this seems less likely.
I have been programming LV for about 7 years and switched from LV 6.1 to 7.1 about four months ago. I know NI engineers have put thousands of hours developing and testing LV 7.1, but honestly I find myself wishing I had never upgraded from using LV 6.1. (To whomever thought "hide trailing zeros" should be the default for floating point controls...what were you thinking?!)
I know each new version of LabView causes old-timers like me to grouse that things were better back in the days when we etched our block diagrams on stone tablets, etc., and honestly I'm not going to go back. I am committed to LabView 7.1. I just wish it were not so slow on my big projects!
Attachments:
LV_Speed_Test.vi ‏22 KB

Hi,
I can confirm this behavior. Setting the execution system to "user
interface" helps a bit, but there is still a big difference.
I get a feeling it has something to do with window messages, perhaps
WM_PAINT or something, that is handled differently if a VI is not
frontmost... But what do I know...
Don't know if it should be called a bug, but it sure is something that could
be optimized.
Regards,
Wiebe.
"Rob Calhoun" wrote in message
news:[email protected]...
> I'm posting this issue to the forums prior to submitting a bug report
> to ensure that the problems I'm having are reproducible. To reproduce
> this bug, you're going to have to be an advanced user with a large
> project (hundreds to thousands of VIs) as the performance problem is
> related to the number of VIs loaded.
>
> The issue is the increasingly poor performance of the LabVIEW 7.1
> Development Environment as the number of VIs in memory increases. The
> actions affected include switching between front panel and diagram,
> saving a VI, copy and paste, clicking a menu, and the mysterious time
> spent (compiling? editing the runtime menu? changing the toolbar
> state?) between pressing the run button and when the code actually
> starts executing. Scrolling and, interestingly, copying via a
> control-drag are not affected. Running time of entirely on-diagram
> code does not seem to be affected.
>
> These problems are quite severe and significantly decrease my
> productivity as a programmer. Since they are development environment
> UI issues, it's been difficult for me to find a good example VI; the
> best I can do is the attached "LV Speed Test.vi". It doesn't test the
> issues that affect me most, but it seems to suffer from the same
> problem.
>
> This simple VI just shows and hides the menu bar 100 times in a tight
> for loop. When it is the only VI loaded, it executes in about 350 msec
> on my machine. (2.4 GHz P-IV/640 MB RAM/Win2k). However, when I load a
> single project-encompassing VI (let's call it the "giant") that
> references a total of about 900 user and VI-lib subVIs, the test
> routine takes almost a minute and half to run...about 240 times
> slower! I've tried this on my laptop with similar results.
>
> The problem appears to be related to the *number* of VIs loaded and
> not the memory utilization. For example, if I close the "giant", and
> create a new VI ("memhog") that does nothing but initialize a length
> 20,000,000 array of doubles and stores it in an uninitialized shift
> register, LabView's overall memory usage (as shown in the task
> manager) jumps enormously, but LV Speed Test executes in about 450
> msec...only slightly slower than with a fresh copy of Labview.
>
> The problem seems to be related to excessive context switching. The
> Windows task manager shows over a thirteen hundred page faults occur
> when "LV Speed Test" is run with the "giant" in the background, versus
> zero or none when run by itself or when "memhog" has used up 160+MB of
> space.
>
> The problem only seems to affect the frontmost window. (Unfortunately,
> that's where we LV programmers spend all of our time!) If you start
> "LV Speed Test" and then put "giant" in the foreground "LV Speed Test"
> runs much faster. In fact, if you use the VI server to put the "giant"
> VI in the foreground programmatically at the start of "LV Speed Test",
> execution time drops back to 450 msec, and there are no page faults!
>
> These results show the issue is not related to video drivers or the
> Windows virtual memory system. My suspicion is that there is a faulty
> routine in LV 7.1 that is traversing the entire VI hierarchy every
> time certain events are thrown in the foreground window. It could be
> due to a problem with the Windows event tracking system, but this
> seems less likely.
>
> I have been programming LV for about 7 years and switched from LV 6.1
> to 7.1 about four months ago. I know NI engineers have put thousands
> of hours developing and testing LV 7.1, but honestly I find myself
> wishing I had never upgraded from using LV 6.1. (To whomever thought
> "hide trailing zeros" should be the default for floating point
> controls...what were you thinking?!)
>
> I know each new version of LabView causes old-timers like me to grouse
> that things were better back in the days when we etched our block
> diagrams on stone tablets, etc., and honestly I'm not going to go
> back. I am committed to LabView 7.1. I just wish it were not so slow
> on my big projects!

Lightroom 4 performance issues

Hello,
Months ago I switched from Aperture 3 to Lightroom 3 and quickly fell in love with the program.
I switched due to constant freezing and crashes in Aperture 3. I invested time and money to learn Lightroom 3. Performance in Lightroom 3 was superb. Anything I would do with regards to any type of adjustment gave instant results on the screen. Program never crashed or froze onec. Quite frankly, I was shocked in a very positive way.
This was on Macbook Pro i5, 8GB RAM, Hi Res Antiglare screen with Snow Leopard.
I purchased Lightroom 4. I did a clean install of OSX Lion and, clean install of LR4. New catalogs, no importing of anything. LR 4 is sooo slow. It works just like Aperture 3 worked, the precise reason that made me dump it.
The longer LR4 is opened, the slower it becomes. The more adjustments are applied, the slower it becomes. I will use brush and I have to wait to see results. I can't use brush. It takes me 15-30 min to brush small part of the image. I will slide adjustments and wait. I will click on crop tool and wait, wait, wait. I really love this program but I just can't work like that.
Would anyone share some light or advice on what could be done, on what is going on?
Thank you.

Rob,
I am working with NEF files and have done so in LR3. I understand from some reading that one of the benefits from converting files to DNG is that they are faster to work with. So I just copied one of my NEF as DNG and I have been working on it for about 15 minutes applying brush after brush and other adjustments to see if LR4 will slow down. Thus far it has been incredibly faster. I will continue to work on this one image and maybe convert few more to DNG to test but do you think that there might be some issue with NEF format? Another bizzare thing I just noticed is that when I open NEF image, my memory quickly goes up to over 3GB and that's not even during applying adjustments. Working now with DNG, memory is just around 1.3 GB. WHAT IS GOING ON HERE???
I wonder what type of files are other LR4 users that are reporing performance issues working with.
Please share your thoughts.
Thank you.

Performance issues using multiple CC design programs?

Hey! I'm Gwidz, and I'm having some performance issues with my adobe programs. I primarily use Photoshop, InDesign and Illustrator for design work. I find that when I have any two of them open, I experience delays in clicking and dragging using my pen tablet, and laggy zooming in/scrolling. This issue disappears when I only have one program open.
I just bought this laptop to use these programs. Here's the specs:
Operating system: Windows 8 64 bit
Processor: 4th gen intel i7 4700HQ
Ram: 16gb DDR3
Graphics: NVIDIA GeForce GTX 770M 3GB GDDR5
Cost me 2000 bucks on amazon, and I'm pretty disappointed in how things are going right now. I definitely don't think it could be a hardware issue, could it?
I'm using an SSD as my scratch disc, and using the 64 bit versions of all programs that have it. Nothing else running in the background except these programs, and yet still I experience poor performance.
Admitedly, I'm new to windows 8, and I'm learning everything that I can about it in hopes of resolving this issue.
If anyone has any advice, any and all is greatly aprpeciated!

I'm seeing this exact same choppiness and VERY slow response times with the same low use of CPU and memory... WITH JUST ONE APP OPEN! Illustrator.
Macbook Retina Pro, 15 inch.
I've tried with the GPU forced off, and forced on, and on autoswitching.
I've tried clean reinstalls. And reboots. Etc.
This is not hardware related. It's something utterly flawed with the way Illustrator (and InDesign) draw do things. They are just grotesquely inefficient.
The fact that the program/app makes no effort to use more CPU/GPU to speed up responsiveness to the user input is the real indicator of how poorly optimised this code is.
After Effects is better. But it's adaptive degradation STUTTERS grotesquely, and it's actually better to try to turn that off. Although I'm having a hard time trying to figure out how to turn that off at the moment.. forgotten where I previously found that switch.
Photoshop is also better.
I'm also talking about small files. Nothing in them. Just start drawing... Stutters... atrocious frame rates for the update of the screen and very poor response rates to input.
This is 64 bit optimised? I don't think so.

Performance issue with MSEG table

Hi all,
I need to fetch materials(MATNR) based on the service order number (AUFNR) in the selection screen,but there is performance isssue with this , how to over come this issue .
Regards ,
Amit

Hi,
There could be various reasons for performance issue with MSEG.
1) database statistics of tables and indexes are not upto date.
because of this wrong index is choosen during the execution.
2) Improper indexes, because there is no indexes with the fields mentioned in the WHERE clause of the statement. Because of this reason, CBO would have choosen wrong index and did a range scan.
3) Optimizer bug in oracle.
4) Size of table is very huge, archive.
Better switch on ST05 trace before you run this statements, so it will give more detailed information, where exactly time being spent during the execution.
Hope this helps
dileep

Adobe Premiere 4 Elements 4 performance issue

Hi
I am a new user of Premiere 4 Elements and I completed my first project to get myself through the learning curve. However I experience a serious performance issue on my computer with this product. Sorry about the long post, I tried to give as complete info as possible. Thanks in advance for any advice on solving the issue.
1. When I open my project, a progress bar stays for several minutes at the near-completed state before the application window opens. Then the window is still frozen for several more minutes (the Windows hourglass displays for about 4 to 5 minutes) before I can actually start using the program.
2. When I task-switch (e.g. to edit a photo in another application, or to check in Windows Explorer where a file is that I want to open) task-switching is slow, and when I switch back to Premiere 4 Elements, the screen freezes again for several minutes (4 to 6 minutes) before I can continue working. Same happens after I used the option to add media from Hard Drive to the project.
3. When I press the Play button, the sound sometimes plays while the video preview gets stuck on a single frame. When I wait a while, it seems like Premiere is busy updating the icons on the timeline, and after that, I can play the video again. Sometimes the screen freezes so I canot press the pause button, and the audio just continues playing for a minute or two.
4. Last night I eventually got the project finished, and started rendering the project to a PAL DVD - quality MPEG. It was still rendering this morning, with the progress bar showing less than a third of progress. At last check it displayed an estimated 16 hours of predicted rendering time, and still increasing the time....
5. In one week of use, I experienced one to five crashes per evening while using this product.
My input files for the project are existing MPEG files that I loaded from the camera (with it's software) long before I purchased Adobe Premiere. (so I did not use Premiere's feature to import the video). This camera generates a new MPEG file each time you press the start/stop button. I can see hundreds of clips on the camera when I mount it as an external USB hard drive on Windows. I suspect the number of files has to do with my issues, so I need assistance on an improved workflow, given the source format I work with. In my test project the original footage consists of about 140 MPEG clips; about 15 photos sized to PAL DVD size (720 x 5xx), one imported DVD VOB file, and then a menu, a title or two, transition effects, and so on. The final project should render 30 minutes of video, but the original footage is about three times that duration. Can someone please suggest a workflow considering the possibility that I will have to deal with these hundreds of small clips?
The software's box specifies a Pentium 4 and 512 Mb RAM, Direct-X compatibility and 4 Gb HDD space.
My computer spec's are:
Intel Core 2, 2.13 GHz,
2 Gb DDR RAM,
200Gb Serial ATA HDD, with:
Premiere on partition C: with 25 Gb free,
Project on partition D: with 40 Gb free.
Very entry-level graphics card (purchased the PC with no thought of games or video).
XP Home is installed.
In Windows Task Manager I notice about One Million Page faults being generated for Adobe Premiere in the periods I mentioned above when Premiere gets stuck. Item 4 above was at 3.5 million page faults with about 25% progress indicated of the rendering process. Is this indicative that I need more RAM?
I have read other posts on this forum that people advise users to have Premiere on one HDD, the swap file on another physical disc and the project on yet another. I can understand the logic, but I checked that my PC was well above the software specifications on the box before I purchased, and I am not so serious about making videos that I would want to upgrade to such a monster PC. Besides if the requirements are such, Adobe should have specified that on the box.
Thanks, Willem

Willem,
Looking at your system specs., I see one major bottleneck - your I/O system. You have a partitioned HDD.
This means that the heads on your HDD are being asked to be in several places at the same time. Partitioning is an element left over from a much earlier time in computing and should not be used nowadays, with very few exceptions. I will explain. You have a fixed number of platters and heads on a single HDD. Those heads are what access the data on the platters. In the case of PE, you are asking the heads to be:
1.) reading the OS
2.) reading Premiere (your program)
3.) reading & writing the Windows Page File (Windows' Virtual Memory)
4.) reading & writing your media Assets (depending on what you're doing)
5.) reading & writing your Scratch Disk data
6.) reading & writing data for any other Process that requires it
The first step that I'd take would be to add another HDD, and do away with the partition on you Drive0. With two physical (not logical as you have) HDDs, the ideal setup would be:
1.) OS and all programs on C:\
2.) Project, Media and Scratch Disks on D:\
Things would even better, though not to the %, that adding only one additional disk, if you added two. Ideal setup for 3 HDDs would be:
1.) OS and all programs on C:\
2.) Media and additional Assets on D:\
3.) Project and Scratch Disks on E:\
I've also found speed increases by having my Windows' Page File on a separate HDD, but that is overkill, really. Now, I've got 5 internals with 1.75TB of space, so it's easy for me to do this sort of thing.
You have a 200GB SATA HDD (Drive0), and I'd keep that for your C:\ (no partition) and add another SATA in 500GB - 1TB range. If you have SATA II, make sure to go with a new HDD with the exact same connector (SATA, or SATA II). Most on-board controllers can handle 4x SATA channels, so it should not be a big deal.
Most work will come from having to do a complete system backup of your Drive0 (your C:\ & D:\), as you'll need re-partition it. Another way around this would be to leave the C:\ & D:\ partitions, and just move all of your Media, Assets, Project and Scratch Disks to your new physical drive. Keep your D:\ partition, but use it only for storing maybe Audio Assets, that you use infrequently, and the like. Do not partition your new HDD (drive1).
Note on load time: that will speed up somewhat, if you get another HDD, but PE does need time to read it's XML files, that tell it the location of all Assets, then go find them, and verify that they are correct. Only a bit of a speed up there. Almost everything else that you mention, regarding speed, will improve greatly.
Others will have some more ideas, on ways to speed things up, and I'd consider them all, plus the addition of another fast, large physical HDD.
BTW: great post. It is probably the most complete that I've seen in any of the Adobe forums. It's easy to read (good use of paragraphs) and contains all the data, that I could want. I'd hold this up as a model on how to ask a question on these boards.
Good luck,
Hunt
[EDIT] To let you know, I actually have my Drive0 (500GB SATA II) partitioned (for another reason) and use it just like my second suggestion, re: re-partitioning. My "Movie Music," SFX and minor Assets are stored on my D:\, plus I have my Windows' Page File split over three drives. This after much experimentation. I'd not recommend this, unless you have a lot of extra time on your hands. Just keep it on C:\

Dynamically-Launched VIs and Context Switching

I'm working on a project that dynamically calls instances of a reentrant VI, which I assume is a pretty common practice. Everything works pretty well, until the number of calls to this dynamic VI gets pretty large--on the order of 1000 or more--at which point, we begin to see performance degradation. My guess is that we are taking hits due to context switching, since the number of threads far exceeds the number of logical processor cores available.
A little more background:
The dynamic VIs being called effectively run as daemons, each running a while loop and waiting on a dedicated input queue to receive data and save it to disk. All are stopped via a globally shared stop notifier (passed as a ControlValue.Set method argument at launch). Each is waiting on its respective queue with a 1 second timeout so that the stop notifier can be polled. Under normal operating conditions, each one will run at some rate between 0.1Hz and 25Hz (the various rates are a large driving factor for separating them and needing to spawn them dynamically).
So, this leads me to the following questions:
Am I correct that the context switching is the likely culprit in the performance degradation?
If so, is there a fundamental difference in how LabVIEW handles multithreading with dynamic VI calls versus explicitly drawing separate while loops on a block diagram, or dropping multiple instances of a reentrant VI directly on the block diagram?
Is it likely that reducing the number of dynamic clones to equal the number of available processor cores would improve performance? (the scope of each clone would grow, as it would have to maintain the state information that was original distributed across multiple clones)
I realize that this question is pretty vague without concrete examples, but I'm hoping someone (AQ? Ben? Any of you NI gurus?) out there could provide some general insight into what's going on under the hood without needing to get too specific.

TurboPhil wrote:
Each is waiting on its respective queue with a 1 second timeout so that the stop notifier can be polled.
There is one relatively easy fix you can probably make here - set the timeout to -1 and destroy the queues to stop the loop (destroying the queue will output an error from the wait primitive). This should at least stop all the code from running all the time, although I'm still not sure how the threading of the different VIs will play with each other. This might be an issue if the queue is only created in the VI, but I'm assuming it isn't.
Try to take over the world!

E7-00 performance issue: screen context switch cau...

Similar Messages

Maybe you are looking for