Improve performance MAX HEAP?

Hello,
We are trying to improve performance of one of our interfaces FILE->SQL STAGING->TARGET.
Here are the steps we took;
1. We are indeed using LKM SQL BULK INSERT (which brought the performance down from 70min to 20min)
*2. The ARRAY and FETCH sizes "DONOT" seem to improve performance at all. Probably because we are using FILE TECHNOLOGY. Experts please confirm this?*
3. Finally, we changed the JAVA INT and MAX sizes from;
INT: 32m to 1024m
MAX: 256m to 2g
a. How do we ensure that the odiparam changes have taken affect? We have been just closing all ODI Navigators, stopping agent and restarting agent. Is this correct?
But it "DIDNT" improve performance either.
Here is what we noticed:
Total Physical Memory is 8G
Physical Memory used is 3.6G
ODI64.exe is using 0.5 G
Java.exe is using 0.5 G
We noticed that Java.exe was "not" using any CPU.
b. Is ODI64.exe what we should be looking at to monitor performance? Shouldn't it be at 2G?
c. Is there a way to define more than one CPU to be used, parallel processing?
Please let me know your thoughts.
Thanks!
Edited by: user10678366 on May 18, 2013 9:09 AM
Edited by: user10678366 on May 18, 2013 9:17 AM

#a Changes in odiparams would be applicable only for the standalone agent. Bouncing the standalone agent would pick the latest settings from odiparams.
#b The min heap size you have specified is 1G so your jvm should have initialized with at least that much memory. Since the processes you mentioned are using lesser memory, it seems that either your memory are not picked up or you are looking at the wrong processes.
#c Depending upon your interface if there is data to be moved row by row through ODI then the reading an writing automatically happens in parallel.

Similar Messages

Siginficance of max heap size mentioned in configtool

Hi all,
could anyone please tell me the exact significance of
max heap size mentioned in configtool in SAP Netweaver in
1)Instance_ID
-servers general
-message servers and bootstrap
2)Dispatcher_ID
-general
-bootstrap
3)Server_ID
-general
-bootstrap
Which of these do i change to improve the performance?
I tried changing the max heap size specified in
Server_ID
-general
but i got the following error while trying to start the server in std_server0.out:
node name : server0
pid : 3452
system name : N02
system nr. : 01
started at : Tue Mar 20 21:53:37 2007
Reserved 1610612736 (0x60000000) bytes before loading DLLs.
[Thr 1912] MtxInit: -2 0 0
Error occurred during initialization of VM
Could not reserve enough space for object heap
Regards,
Namrata.

Hi,
The biggest impact to runtime performance will be adjusting the heap size of the server JVM. This is done in Server_ID->general. The JVM parameters entered here take precedence over parameters in Instance_ID->servers general. The server job by far do the most work in the Java engine and so it is very important that the JVM for the server node is tuned to handle the workload. Tuning the server JVM or even adding additional server nodes is dependent on the workload and the amount of work on the system.
Adjusting the heap for the other JVMs will have much less of an impact than adjusting the heap in the server JVM.
The dispatcher JVM heap settings may have a slight impact during runtime, but compared to the server jobs the dispatcher does relatively little work. Depending on your situation you may need to tune the dispatcher a little, but my experience has been that the default value for the dispatcher is usually sufficient.
The values for all of the bootstrap jobs may have an impact on startup time, but they will have no impact on runtime since these jobs go away once the system is up. From what I have seen the defaults values for the bootstrap jobs are sufficent.
I never adjust anything under Instance_ID, I'm not sure what these parameters are used for except for maybe default values when adding server nodes. Maybe someone out there knows.
Hope this helps.
Regards,
Kolby

Allocated Heap v.s. Max Heap and OutOfMemoryError

In my application, I specify heap size like following:
-Xms384m -Xmx384m
I got few OOME error recently. From our monitoring tool, I can see the 'allocated heap' was only about 280 - 340MB range when OOME happened. That means that the used heap size were close or reach the 'allocated' heap size but not the max heap that defined in '-Xmx'. My question is:
Why does JVM act like this? What is the problem that prevents JVM from obtaining promised memory from OS?
We are using JDK 1.5
Thanks,
J

Its easy to check this, create as many threads as possible and configure a small heap size and a big stack size, count the number of created threads, then increase the heap and run the program again. Then you can see the number of threads increased too.
I have created a [java program to do exactly this, check it out|http://weblogs.java.net/blog/claudio/archive/2007/05/how_many_thread_1.html] .
See below, how thread stack size are allocated into the heap.
[http://java.sun.com/docs/hotspot/threads/threads.html|http://java.sun.com/docs/hotspot/threads/threads.html]
excerpt "TLEs (in 1.3) or TLABs (in 1.4) are thread local portions of the heap used in the young generation"
[Java Memory White Paper|http://java.sun.com/javase/technologies/hotspot/gc/memorymanagement_whitepaper.pdf]
For multithreaded applications, allocation operations need to be multithread-safe. If global locks were used to
ensure this, then allocation into a generation would become a bottleneck and degrade performance. Instead,
the HotSpot JVM has adopted a technique called Thread-Local Allocation Buffers (TLABs). This improves
multithreaded allocation throughput by giving each thread its own buffer (i.e., a small portion of the
generation) from which to allocate. Since only one thread can be allocating into each TLAB, allocation can take
place quickly by utilizing the bump-the-pointer technique, without requiring any locking. Only infrequently,
when a thread fills up its TLAB and needs to get a new one, must synchronization be utilized. Several techniques
to minimize space wastage due to the use of TLABs are employed. For example, TLABs are sized by the allocator
to waste less than 1% of Eden, on average. The combination of the use of TLABs and linear allocations using the
bump-the-pointer technique enables each allocation to be efficient, only requiring around 10 native instructions.

Improve performance by less server calls

Hi,
I have a problem with an application that are to slow. One of the
problems is that the client calls the server alot of times. What I would
like to do (what I should have done from the start) is minimize the calls
to the server. But the calls are scattered around the client code so I
can�t see an easy way of doing this.
(Every server call go through a class called ServerInteractor.)
I think this might be a very common newbie mistake, so I hope there is
someone out there who knows a way to solve this.
Thanks!

Thanks for your replies!
My experience is that if your app is taking too longto load, it's likely the amount of data you are
retrieving, not the number of times you call the
server
Do you think this might vary if you have a slow or
fast network-connection?We had this problem on a local network. A slow network would just be worse. Actually, we had to support slow connections (56K) so we ended up compressing the messages.
Most likely caching the screen after the first timeyou get the information about it and reusing that
cached version will yield better performance
I have implemented a client cache that caches
information about the
windows. This was the solution we came up with for the 'big spit-ball' message pattern. We cached as much information as possible. On shutdown of the app, we serialized the cache to disk. We implemented a small message that would report when parts of the cache items were no longer valid. By making the cache block the client, we were able to do this seamlessly.
This improves performence alot! The second
time you open
a window it takes 4 seconds instead of 25.
But now I am facing another problem. After runing the
app for a while I
get an outOfMemoryError. Before the client cache I
never got this error,
but now it always comes after I run the app for a
while. So this makes
me think that the cache "is to be blamed". Is this a
sign for a bug in my
caching code? I have read that you can increase the
memory when you
start the app, but is that a guarantee for this never
to happen?From your description, it sounds like increasing the max heap size will merely delay the error.
You've got two options at this point: 1. Start looking through the code for the cache and make sure you are not holding onto expired information. 2. Get a profiling tool and use it to figure out where the leak is.
I would attempt 1. since you just wrote the cache but I find that guis are the worst for sneaky leaks. Watch out for inner classes (not static nested classes) because they contain a hidden reference to the outer instance.

How do I improve performance while doing pull, push and delete from Azure Storage Queue

Hi,
I am working on a distributed application with Azure Storage Queue for message queuing. queue will be used by multiple clients across the clock and thus it is expected that it would be heavily loaded most on the time in usage. business case is typical as in
it pulls message from queue, process the message then deletes the message from queue. this module also sends back a notification to user indicating process is complete. functions/modules work fine as in they meet the logical requirement. pretty typical queue
scenario.
Now, coming to the problem statement. since it is envisaged that the queue would be heavily loaded most of the time, I am pushing towards to speed up processing of the overall message lifetime. the faster I can clear messages, the better overall experience
it would be for everyone, system and users.
To improve on performance I did multiple cycles for performance profiling and then improving on the identified "HOT" path/function.
It all came down to a point where only the Azure Queue pull and delete are the only two most time consuming calls outside. I can further improve on pull, which i did by batch pulling 32 message at a time (which is the max message count i can pull from Azure
queue at once at the time of writing this question.), this returned me a favor as in by reducing processing time to a big margin. all good till this as well.
i am processing these messages in parallel so as to improve on overall performance.
pseudo code:
//AzureQueue Class is encapsulating calls to Azure Storage Queue.
//assume nothing fancy inside, vanila calls to queue for pull/push/delete
var batchMessages = AzureQueue.Pull(32); Parallel.ForEach(batchMessages, bMessage =>
//DoSomething does some background processing;
try{DoSomething(bMessage);}
catch()
//Log exception
AzureQueue.Delete(bMessage);
With this change now, profiling results show that up-to 90% of time is only taken by the Azure Message delete calls. As it is good to delete message as soon as processing is done, i remove it just after "DoSomething" is finished.
what i need now is suggestions on how to further improve performance of this function when 90% of the time is being eaten up by the Azure Queue Delete call itself? is there a better faster way to perform delete/bulk delete etc?
with the implementation mentioned here, i get speed of close to 25 messages/sec. Right now Azure queue delete calls are choking application performance. so is there any hope to push it further.
Does it also makes difference in performance which queue delete call am making? as of now queue has overloaded method for deleting message, one which except message object and another which accepts message identifier and pop receipt. i am using the later
one here with message identifier nad pop receipt to delete message from queue.
Let me know if you need any additional information or any clarification in question.
Inputs/suggestions are welcome.
Many thanks.

The first thing that came to mind was to use a parallel delete at the same time you run the work in DoSomething. If DoSomething fails, add the message back into the queue. This won't work for every application, and work that was in the queue
near the head could be pushed back to the tail, so you'd have to think about how that may effect your workload.
Or, make a threadpool queued delete after the work was successful. Fire and forget. However, if you're loading the processing at 25/sec, and 90% of time sits on the delete, you'd quickly accumulate delete calls for the threadpool until you'd
never catch up. At 70-80% duty cycle this may work, but the closer you get to always being busy could make this dangerous.
I wonder if calling the delete REST API yourself may offer any improvements. If you find the delete sets up a TCP connection each time, this may be all you need. Try to keep the connection open, or see if the REST API can delete more at a time
than the SDK API can.
Or, if you have the funds, just have more VM instances doing the work in parallel, so the first machine handles 25/sec, the second at 25/sec also - and you just live with the slow delete. If that's still not good enough, add more instances.
Darin R.

A64 Tweaker and Improving Performance

I noticed a little utility called "A64 Tweaker" being mentioned in an increasing number of posts, so I decided to track down a copy and try it out...basically, it's a memory tweaking tool, and it actually is possible to get a decent (though not earth-shattering by any means) performance boost with it. It also lacks any real documentation as far as I can find, so I decided to make a guide type thing to help out users who would otherwise just not bother with it.
Anyways, first things first, you can get a copy of A64 Tweaker here: http://www.akiba-pc.com/download.php?view.40
Now that that's out of the way, I'll walk through all of the important settings, minus Tcl, Tras, Trcd, and Trp, as these are the typical RAM settings that everyone is always referring to when they go "CL2.5-3-3-7", so information on them is widely available, and everyone knows that for these settings, lower always = better. Note that for each setting, I will list the measured cange in my SiSoft Sandra memory bandwidth score over the default setting. If a setting produces a change of < 10 MB/sec, its effects will be listed as "negligible" (though note that it still adds up, and a setting that has a negligible impact on throughput may still have an important impact on memory latency, which is just as important). As for the rest of the settings (I'll do the important things on the left hand side first, then the things on the right hand side...the things at the bottom are HTT settings that I'm not going to muck with):
Tref - I found this setting to have the largest impact on performance out of all the available settings. In a nutshell, this setting controls how your RAM refreshes are timed...basically, RAM can be thought of as a vast series of leaky buckets (except in the case of RAM, the buckets hold electrons and not water), where a bucket filled beyond a certain point registers as a '1' while a bucket with less than that registers as a '0', so in order for a '1' bucket to stay a '1', it must be periodically refilled (i.e. "refreshed"). The way I understand this setting, the frequency (100 MHz, 133 MHz, etc.) controls how often the refreshes happen, while the time parameter (3.9 microsecs, 1.95 microsecs, etc.) controls how long the refresh cycle lasts (i.e. how long new electrons are pumped into the buckets). This is important because while the RAM is being refreshed, other requests must wait. Therefore, intuitively it would seem that what we want are short, infrequent refreshes (the 100 MHz, 1.95 microsec option). Experimentation almost confirms this, as my sweet spot was 133 MHz, 1.95 microsecs...I don't know why I had better performance with this setting, but I did. Benchmark change from default setting of 166 MHz, 3.9 microsecs: + 50 MB/sec
Trfc - This setting offered the next largest improvement...I'm not sure exactly what this setting controls, but it is doubtless similar to the above setting. Again, lower would seem to be better, but although I was stable down to '12' for the setting, the sweet spot here for my RAM was '18'. Selecting '10' caused a spontaneous reboot. Benchmark change from the default setting of 24: +50 MB/sec
Trtw - This setting specifies how long the system must wait after it reads a value before it tries to overwrite the value. This is necessary due to various technical aspects related to the fact that we run superscalar, multiple-issues CPU's that I don't feel like getting into, but basically, smaller numbers are better here. I was stable at '2', selecting '1' resulted in a spontaneou reboot. Benchmark change from default setting of 4: +10 MB/sec
Twr - This specifies how much delay is applied after a write occurs before the new information can be accessed. Again, lower is better. I could run as low as 2, but didn't see a huge change in benchmark scores as a result. It is also not too likely that this setting affects memory latency in an appreciable way. Benchmark change from default setting of 3: negligible
Trrd - This controls the delay between a row address strobe (RAS) and a seccond row address strobe. Basically, think of memory as a two-dimensional grid...to access a location in a grid, you need both a row and column number. The way memory accesses work is that the system first asserts the column that is wants (the column address strobe, or CAS), and then asserts the row that it wants (row address strobe). Because of a number of factors (prefetching, block addressing, the way data gets laid out in memory), the system will often access multiple rows from the same column at once to improve performance (so you get one CAS, followed by several RAS strobes). I was able to run stably with a setting of 1 for this value, although I didn't get an appreciable increase in throughput. It is likely however that this setting has a significant impact on latency. Benchmark change from default setting of 2: negligible
Trc - I'm not completely sure what this setting controls, although I found it had very little impact on my benchmark score regardless of what values I specified. I would assume that lower is better, and I was stable down to 8 (lower than this caused a spontaneous reboot), and I was also stable at the max possible setting. It is possible that this setting has an effect on memory latency even though it doesn't seem to impact throughput. Benchmark change from default setting of 12: negligible
Dynamic Idle Cycle Counter - I'm not sure what this is, and although it sounds like a good thing, I actually post a better score when running with it disabled. No impact on stability either way. Benchmark change from default setting of enabled: +10 MB/sec
Idle Cycle Limit - Again, not sure exactly what this is, but testing showed that both extremely high and extremely low settings degrade performance by about 20 MB/sec. Values in the middle offer the best performance. I settled on 32 clks as my optimal setting, although the difference was fairly minimal over the default setting. This setting had no impact on stability. Benchmark change from default setting of 16 clks: negligible
Read Preamble - As I understand it, this is basically how much of a "grace period" is given to the RAM when a read is asserted before the results are expected. As such, lower values should offer better performance. I was stable down to 3.5 ns, lower than that and I would get freezes/crashes. This did not change my benchmark scores much, though in theory it should have a significant impact on latency. Benchmark change from default setting of 6.0 ns: negligible
Read Write Queue Bypass - Not sure what it does, although there are slight performance increases as the value gets higher. I was stable at 16x, though the change over the 8x default was small. It is possible, though I think unlikely, that this improves latency as well. Benchmark change from default setting of 8x: negligible
Bypass Max - Again not sure what this does, but as with the above setting, higher values perform slightly better. Again I feel that it is possible, though not likely, that this improves latency as well. I was stable at the max of 7x. Benchmark change from the default setting of 4x: negligible
Asynch latency - A complete mystery. Trying to run *any* setting other than default results in a spontaneous reboot for me. No idea how it affects anything, though presumably lower would be better, if you can select lower values without crashing.
...and there you have it. With the tweaks mentioned above, I was able to gain +160 MB/sec on my Sandra score, +50 on my PCMark score, and +400 on my 3dMark 2001 SE score. Like I said, not earth-shattering, but a solid performance boost, and it's free to boot. Settings what I felt had no use in tweaking the RAM for added performance, or which are self-explanatory, have been left out. The above tests were performed on Corsair XMS PC4000 RAM @ 264 MHz, CL2.5-3-4-6 1T.

Quote
Hm...I wonder which one is telling the truth, the BIOS or A64 tweaker.
I've wondered this myself. From my understanding it the next logic step from the WCREDIT programs. I understand how clock gen can misreport frequency because it's probably not measuring frequency itself but rather a mathmatical representation of a few numbers it's gathered and one clk frequency(HTT maybe?), and the non supported dividers messes up the math...but I think the tweaker just extracts hex values strait from the registers and displays in "English", I mean it could be wrong, but seeing how I watch the BIOS on The SLI Plat change the memory timings in the POST screen to values other then SPD when it Auto with agressive timings in disabled, I actually want to side with the A64 tweaker in this case.
Hey anyone know what Tref in A64 relates to in the BIOS. i.e 200 1.95us = what in the BIOS. 1x4028, 1x4000, I'm just making up numbers here but it's different then 200 1.95, last time I searched I didn't find anything. Well I found ALOT but not waht I wanted..

Strange: Mac screen menu-bar requires max-heap-size to be set.

I planned to omit the max-heap-size attribute in the line of my jnlp file
<j2se version="1.6+" max-heap-size="256m" />
The idea was that with Java 1.6 the heap size is set automatically
according to the client's RAM.
Unfortunately, the Macintosh screen menu-bar works if and only if the max-heap-size attribute is present.
It is a MacOsX=1.4 with Java1.5.
Strange, since the Mac runs Java 1.5 and I am talking about settings for 1.6.
The jnlp passed ValidateJNLP at http://mindprod.com/jgloss/jnlp.html#VALIDATION
Here is another post stating that attributes in JNLP have side effects on Mac's screen menu-bar:
http://lists.apple.com/archives/Java-dev/2008/Jul/msg00122.html
Here is my jnlp:
w3m -dump http://www.bioinformatics.org/strap/strap.jnlp
Is there an explanation for this?
Christoph

user10289576 wrote:
I would not blame Macintosh.
The error might still be in the Sun's code.Could be. But to fix the Mac VM it would require the following.
1. Find it in the Sun VM.
2. Fix it in the Sun VM.
3. Move the changes to the Mac VM...somehow.
>
If the jdk would be smaller, less redundant and clearer, then
open JDK could be possibly compiled on a Mac.
Not sure what that means since there are likely OS level calls that must be implemented in some place in the API. Which are specific to Mac.
Just as there are differences between windows/solaris/linux which Sun accounted for.
And that would be what Apple would have done to make it work on Mac. And what someone (someone who likes Mac) will need to continue to do with the public release (explusion?) which is the form that Java will have going forward.
The main thing that should be improved on a Macintosh
is to directly allow for Linux and Solaris executables such that the Linux JDK could directly work on a Mac.The main thing, again, is the Apple is no longer supporting Java on the Mac.
And Apple, not Sun and certainly not Oracle, were the ones that created the Java VM.
So the main thing at this point is that ALL future directions that Java take are dependent not on Apple but on the Macintosh community. That includes features as well as fixes.

Peformance Improvement by increasing heap size

Hi
Is there any performace benefit when I execute my Java application by increasing the default heap size using Java -ms200m -mx200m <appName>
Please support with some performance figures
Regards
Vishal

If you know the size of the heap gows to you can save some time on startup. i.e.
If you know it grows to 100 MB on startup, make this the initial size.
The only diference I have found is when using SoftReference caching. Having more heap size will allow such a cahce keep it data for longer.
I would suggest running the application with -verbosegc to soo how often it garbage collects and how long it spends do it.
If you want to improve performance use a profiles e.g. JProfiler, Optimize-It, JProbe

FI-CA events to improve performance

Hello experts,
Does anybody use the FI-CA events to improve the extraction performance for datasources 0FC_OP_01 and 0FC_CI_01 (open and cleared items)?
It seems that this specific exits associated to BW events have been developped especially to improve performance.
Any documentation, guide should be appreciate.
Thanks.
Thibaud.

Thanks to all for the replies
@Sybrand
Please answer first whether the column is stored in a separate lobsegment.
No. Table,Index,LOB,LOB index uses the same TS. I missed adding this point( moving to separate TS) as part of table modifications.
@Hemant
There's a famous paper / blog post about CLOBs and Database Flashback. If I find it, I'll post the URL.
Is this the one you are referring to
http://laimisnd.wordpress.com/2011/03/25/lobs-and-flashback-database-performance/
By moving the CLOB column to different block size , I will test the performance improvement it gives and will share the results.
We dont need any data from this table. XML file contains details about finger prints and once the application server completes the job , XML data is deleted from this table.
So no need of backup/recovery operations for this table. Client will be able to replay the transactions if any problem occurs.
@Billy
We are not performing XML parsing on DB side. Gets the XML data from client -> insert into table -> client selects from table -> Upon successful completion of the Job from client ,XML data gets deleted.
Regarding binding of LOB from client side, will check on that side also to reduce round trips.
By changing the blocksize, I can keep db_32K_cache_size=2G and keep this table in CACHE. If I directly put my table to CACHE, it will age out all other operation from buffer which makes things worse for us.
This insert is part of transaction( Registration of a finger print) and this is the only statement taking time as of now compared to other statements in the transaction.
Thanks,
Arun

How to preload sound into memory to improve performance?

Hello all
I have an application where it needs to play 4 different short wave files on some events. The wave files are small (less then 1 sec each) so they can be preloaded into memory. But I don't really know how to do that.. This is my current code... Performance is really important here, so the faster users can hear the sounds, the better...
import java.io.*;
import javax.sound.sampled.*;
import javax.swing.*;
import java.awt.event.*;
public class PlaySound implements ActionListener
     private Clip clip = null;
     public void play(String name)
          if (clip != null)
               clip.stop();
               clip = null;
          loadClip(name);
          clip.start();
     private void loadClip(String fnm)
          try
               AudioInputStream stream = AudioSystem.getAudioInputStream(new File(fnm + ".wav"));
               AudioFormat format = stream.getFormat();
               DataLine.Info info = new DataLine.Info(Clip.class, format);
               if (!AudioSystem.isLineSupported(info))
                    JOptionPane.showMessageDialog(null, "Unsupported sound line", "Warning!", JOptionPane.WARNING_MESSAGE);
               else
                    clip = (Clip) AudioSystem.getLine(info);
                    clip.open(stream);
                    stream.close();
          catch (Exception e)
               JOptionPane.showMessageDialog(null, "loadClip E: " + e.toString(), "Warning!", JOptionPane.WARNING_MESSAGE);
     public static void main(String[] args)
          play("a wav file name");
}     I would appreciate it if someone can point out how I can preload them to improve performance... Thanks in advance!

The message above should be:
OMG, me dumb you smart Florian...
Thank you for your suggestion... It's not the best OR anything close to what I thought it would be, it's certainly one way to do it and better then what I've got now...
Thanks again Florian, I really appreciate it!!
BTW, is there anything that would produce the sound faster then this?
Message was edited by:
BuggyVB

How to improve performance of MediaPlayer?

I tried to use the MediaPlayer with a On2 VP6 flv movie.
Showing a video with a resolution of 1024x768 works.
Showing a video with a resolution of 1280x720 and a average bitrate of 1700 kb/s leads to a delay of the video signal behind the audio signal of a couple of seconds. VLC, Media Player Classic and a couple of other players have no problem with the video. Only the FX MediaPlayer shows a poor performance.
Additionally mouse events in a second stage (the first stage is used for the video) are not processed in 2 of 3 cases. If the MediaPlayer is switched off, the mouse events work reliable.
Does somebody know a solution for this problems?
Cheers
masim

duplicate thread..
How to improve performance of attached query

How to improve performance when there are many TextBlocks in ItemsControl items?

Hi,
I'm trying to find a way to improve performance for a situation when there is an ItemsControl using UI and Data virtualization and each item on that control has 36 TextBlocks. Basically the item is a single string. There are so many TextBlocks
to allow assigning different brushes to different parts of the string. Performance of this construction is terrible. I have 37 items visible on the screen and if I try to scroll up or down it scrolls into the black space and then it takes a second or two to
show the items.
I tried different things. For example, the most successful performance-wise was to replace TextBlocks with Borders and then draw bitmaps. In other words, I prepared 127 bitmaps for each character (I need ASCII only) and then I used those bitmaps
to set Border.Backgrounds. It improved performance about 1.5 - 2 times but it consumed much more memory (which is not surprising, of course). Required amount of memory is so big that it throws OutOfMemoryException on 512MB emulator but works on 1GB. As a result
I don't thing it is a good solution.
Another thing that worked perfect is to replace 36 TextBlocks with only 6 TextBlocks. In this case the performance improvement is about 5 - 10 times but I lose the ability to set different colors to different parts of the string. It seems that
the performance degrades dramatically with the increase of number of TextBlocks. Is there another technique to draw strings where literally each character can be of different color with decent performance?
Thank you
Alex

Using Runs inside TextBlocks gives approximately the same improvement as using bitmaps 1.5 - 2 times faster but it is not even close to the case with just a couple of TextBlocks in the ItemsControl item. Any other ideas?
Alex

How to improve Performance of the Statements.

Hi,
I am using Oracle 10g. My problem is when i am Execute & fetch the records from the database it is taking so much time. I have created Statistics also but no use. Now what i have to do to improve the Performance of the SELECT, INSERT, UPDATE, DELETE Statements.
Is it make any differents because i am using WindowsXP, 1 GB RAM in Server Machine, and WindowsXP, 512 GB RAM in Client Machine.
Pls. Give me advice for me to improve Performance.
Thank u...!

What and where to change parameters and values ?Well, maybe my previous post was not clear enough, but if you want to keep your job, you shouldn't change anything else on init parameter and you shouldn't fall in the Compulsive Tuning Disorder.
Everyone who advise you to change some parameters to some value without any more info shouldn't be listen.
Nicolas.

I have a MAC Pro from 2011 currently running MAC OS 10.9.5. This weekend I cloned the MAC HD drive to a new SSD drive for improved performance. The clone was completed successfully with no errors. After the clone completed I successfull restarted my sy

I have a MAC Pro from 2011 currently running MAC OS 10.9.5. This weekend I cloned the MAC HD drive to a new SSD drive for improved performance. The clone was completed successfully with no errors. After the clone completed I successfully restarted my system using the SSD as the boot device. I then successfully tested all of my products, including Photoshop CS6 and all of its plug-ins. I successfully tested the key features that I frequently use. Today while attempting to launch Photoshop CS6 a message is being displayed indicating that a scratch disk cannot be found. All drives are available on the system via the Finder and Disk Utility. I can access all drives including the old MAC HD which is no longer the boot device. I've even attempted to launch Photoshop from the old device yet the same error persist. Is there a way to review/edit/change Photoshop preferences if Photoshop doesn't launch? I've even restarted my system several times to see if that would resolve the issues. Does anyone have any recommendations for this issue? Have you previously address this issue?
Thank you Gregg Williams

Boilerplate text:
Reset Preferences
http://forums.adobe.com/thread/375776
1) Close the program and press Ctrl+Alt+Shift/Cmd+Option+Shift during startup (not reversible)
or
2) Move the Folder. See:
http://www.bugge.com/Family-and-friends/Illy/illy.html
--OB

How to set max-heap-size outside the jnlp file?

Due to bug_id=6631056 It may not be possible to specify max-heap-size within
the JNLP file for certain jnlp java applications.
Are there other possibilities to specify this Jvm parameter?
In the ControlPanel there is the possibility to specify Xmx for applets but not for jnlp.
I have tried to add properties like
"deployment.javaws.jre.0.args=Xmx\=128M" without success
Many thanks

Even in JNLP also you can specify the max heap size
<j2se version="1.5+" initial-heap-size="128m" max-heap-size="512m"/>
Thanks,
Suresh
[http://sureshdevi.co.in|http://sureshdevi.co.in]

Improve performance MAX HEAP?

Similar Messages

Maybe you are looking for