Optimal Size

I'm wondering what might be the maximum useful size for the iPhoto library. I have about 10,000 photos and I see that the library folder is up to 18 gigs. Would it be advantageous to split it up? Thanks.
jor

jor:
If you're running into speed problems then maybe splitting up the library might be helpful but I wouldn't do it unless you are experiencing problems.
DO keep a current backup of the Library6.iPhoto database file as that's the heart of the library and can be irreparably damaged by an interruption of some sort while that file is being written to by iPhoto. By frequent I mean after each import and or any work on books, slideshows, etc. I do it like I do saves when working in my word processor application. Frequently. It's one of the most frequent problems reported here. See the tip at the end of my signature for a way to do that backup frequently and easily.
Also, if you have the space, keep a backup of the entire iPhoto Library folder and keep current with backup applications like Synk. If there's a drive crash you'll want a copy of the library on another media source.
Do you Twango?
TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
I've written an Automator workflow application (requires Tiger), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.

Similar Messages

How do you determine the optimal size for Mozilla Firefox?

How do you determine the optimal size for cache in Mozilla
Firefox? I am using Firefox 7.0.1 on a 64-bit Windows 7 Ultimate operating system with 3GB RAM and 300 GB hard drive, but I have other computers running Windows XP. If the answer doesn't apply to all current versions of Firefox on all supported Windows operating systems, please explain the differences. Is there a formula for calculating the best cache size?

I found that the best idea is to let Firefox decide that itself.

Private strand flush not complete how to find optimal size of redo log file

hi,
i am using oracle 10.2.0 on unix system and getting Private strand flush not complete in the alert log file. i know this is due to check point is not completed.
I need to increase the size of redo log files or add new group to the database. i have log file switch (checkpoint incomplete) in the top 5 wait event.
i can't change any parameter of database. i have three redo log group and log files are of 250MB size. i want to know the suitable size to avoid problem.
select * from v$instance_recovery;
RECOVERY_ESTIMATED_IOS ACTUAL_REDO_BLKS TARGET_REDO_BLKS LOG_FILE_SIZE_REDO_BLKS LOG_CHKPT_TIMEOUT_REDO_BLKS LOG_CHKPT_INTERVAL_REDO_BLKS FAST_START_IO_TARGET_REDO_BLKS TARGET_MTTR ESTIMATED_MTTR CKPT_BLOCK_WRITES OPTIMAL_LOGFILE_SIZE ESTD_CLUSTER_AVAILABLE_TIME WRITES_MTTR WRITES_LOGFILE_SIZE WRITES_LOG_CHECKPOINT_SETTINGS WRITES_OTHER_SETTINGS WRITES_AUTOTUNE WRITES_FULL_THREAD_CKPT
625 9286 9999 921600 9999 0 9 112166207 0 0 219270206 0 3331591 5707793please suggest me or tell me the way how to find out suitable size to avoid problem.
thanks
umesh

How often should a database archive its logs
Re: Redo log size increase and performance
Please read the above thread and great replies by HJR sir. I think if you wish to get concept knowledge, you should add in your notes.
"If the FAST_START_MTTR_TARGET parameter is set to limit the instance recovery time, Oracle automatically tries to checkpoint as frequently as necessary. Under this condition, the size of the log files should be large enough to avoid additional checkpointing due to under sized log files. The optimal size can be obtained by querying the OPTIMAL_LOGFILE_SIZE column from the V$INSTANCE_RECOVERY view. You can also obtain sizing advice on the Redo Log Groups page of Oracle Enterprise Manager Database Control."
Source:http://download-west.oracle.com/docs/cd/B13789_01/server.101/b10752/build_db.htm#19559
Pl also see ML Doc 274264.1 (REDO LOGS SIZING ADVISORY) on tips to calculate the optimal size for redo logs in 10g databases
Source:Re: Redo Log Size in R12
HTH
Girish Sharma

Optimal size of redo log

Hi all,
Recently we migrated from 9.2.0.4 to 10.2.0.4 and database performance is slow in newer version, on checking alert log we found this:-
Thread 1 cannot allocate new log, sequence 1779 Checkpoint not complete
Current log# 6 seq# 1778 mem# 0: /oradata/lipi/redo6.log
Current log# 6 seq# 1778 mem# 1: /oradata/lipi/redo06a.log Wed Mar 10 15:19:27 2010 Thread 1 advanced to log sequence 1779 (LGWR switch)
Current log# 1 seq# 1779 mem# 0: /oradata/lipi/redo01.log
Current log# 1 seq# 1779 mem# 1: /oradata/lipi/redo01a.log Wed Mar 10 15:20:45 2010 Thread 1 advanced to log sequence 1780 (LGWR switch)
Current log# 2 seq# 1780 mem# 0: /oradata/lipi/redo02.log
Current log# 2 seq# 1780 mem# 1: /oradata/lipi/redo02a.log Wed Mar 10 15:21:44 2010 Thread 1 advanced to log sequence 1781 (LGWR switch)
Current log# 3 seq# 1781 mem# 0: /oradata/lipi/redo03.log
Current log# 3 seq# 1781 mem# 1: /oradata/lipi/redo03a.log Wed Mar 10 15:23:00 2010 Thread 1 advanced to log sequence 1782 (LGWR switch)
Current log# 4 seq# 1782 mem# 0: /oradata/lipi/redo04.log
Current log# 4 seq# 1782 mem# 1: /oradata/lipi/redo04a.log Wed Mar 10 15:24:48 2010 Thread 1 advanced to log sequence 1783 (LGWR switch)
Current log# 5 seq# 1783 mem# 0: /oradata/lipi/redo5.log
Current log# 5 seq# 1783 mem# 1: /oradata/lipi/redo05a.log Wed Mar 10 15:25:00 2010 Thread 1 cannot allocate new log, sequence 1784 Checkpoint not complete
Current log# 5 seq# 1783 mem# 0: /oradata/lipi/redo5.log
Current log# 5 seq# 1783 mem# 1: /oradata/lipi/redo05a.log Wed Mar 10 15:25:27 2010 Thread 1 advanced to log sequence 1784 (LGWR switch)
Current log# 6 seq# 1784 mem# 0: /oradata/lipi/redo6.log
Current log# 6 seq# 1784 mem# 1: /oradata/lipi/redo06a.log Wed Mar 10 15:28:11 2010 Thread 1 advanced to log sequence 1785 (LGWR switch)
Current log# 1 seq# 1785 mem# 0: /oradata/lipi/redo01.log
Current log# 1 seq# 1785 mem# 1: /oradata/lipi/redo01a.log Wed Mar 10 15:29:56 2010 Thread 1 advanced to log sequence 1786 (LGWR switch)
Current log# 2 seq# 1786 mem# 0: /oradata/lipi/redo02.log
Current log# 2 seq# 1786 mem# 1: /oradata/lipi/redo02a.log Wed Mar 10 15:31:22 2010 Thread 1 cannot allocate new log, sequence 1787 Private strand flush not complete
Current log# 2 seq# 1786 mem# 0: /oradata/lipi/redo02.log
Current log# 2 seq# 1786 mem# 1: /oradata/lipi/redo02a.log Wed Mar 10 15:31:29 2010 Thread 1 advanced to log sequence 1787 (LGWR switch)
Current log# 3 seq# 1787 mem# 0: /oradata/lipi/redo03.log
Current log# 3 seq# 1787 mem# 1: /oradata/lipi/redo03a.log Wed Mar 10 15:31:40 2010 Thread 1 cannot allocate new log, sequence 1788 Checkpoint not complete
Current log# 3 seq# 1787 mem# 0: /oradata/lipi/redo03.log
Current log# 3 seq# 1787 mem# 1: /oradata/lipi/redo03a.log Wed Mar 10 15:31:47 2010 Thread 1 advanced to log sequence 1788 (LGWR switch)
Current log# 4 seq# 1788 mem# 0: /oradata/lipi/redo04.log
Current log# 4 seq# 1788 mem# 1: /oradata/lipi/redo04a.log
so, my point is should we increase redo log size to fix Checkpoint not complete message, if yes then what should be optimal size of redo log file?
Piyush

Respected Sir,
So many things are going to popular without evidence, experts comments and even cross marking by docs. I would like to suggest to add one more chapter in next oracle release docs something like:
"Myths in Oracle" and i hope following should be there:
1. Put indexes in seperate tablespace to achieve good performance.
2. Different block size issues and its pros and cons.
3. Index scan is always best then full table scan; means if optimizer is not using index means there is something "fishy" with either query or database.
4. Certification is the measurement of good knowledge in oracle.
5. count(1) or count(*) is faster than each other.
(difference between count(*) and count(1) and count(column name)
6. Views are slow
(Do you believe that "views are slow" is a myth
7. BCHR is meaningful indicator for the performance of the database.
(I do'nt want to put the link, because that thread is .... )
8. And this thread i.e. redo log should be large enough to have at least 20 minutes of data.
Sir, since i am regular reader of your site, blog and book; if you please spare some time on above or more myths in oracle; i hope it will help the whole oracle dba community who is something like in a very big and dark hall with lot of doors and windows (as i am).
Kind Regards
Girish Sharma
Edited by: Girish Sharma on Mar 11, 2010 6:27 PM
And i got the useful link of your site please too:
http://www.jlcomp.demon.co.uk/myths.html

Optimal size for TEMP tablespace tempfiles

Hi all,
I've rumaged through Oracle documentation on the above topic but can't find the answer I'm seeking:
How do you determine the optimal size for your tempfiles? Are there rules to guide one in this area? For example for a 50G database, how do you determine if it's 2G, 3G or 4G that's best for the database? What about a 500G database?
Anwers will be appreciated.
Regards

It's the size of the sets, as you say. And in a data warehouse, the data sets can be very large. I'd say that in an OLTP database, then the useage of temp would (should) be low; but in a data warehouse, all bets are off: one-off end of month runs; director wants a monolithic report running; all that sort of DWH-related type of processing, which, by its nature, happens all the time. Similarly, a large number of users (e.g. users of, say, a Third Party BI tool) amy lead to lots of big sorts, owing to the ad hoc nature of their queries. Standard DWH stuff.
I don't often see tiddly-widdly bits of SQL in data warehouses, like your SELECT COUNT(*) FROM tab$ example. It could be done, sure, but more likely will be bit, fat queries, which a DWH is designed to deal with. And a lot of temp may be required.
From that 6-years old (but relevant) article (my emphasis): "For example, if you join two *large* tables, and Oracle cannot do the sort in memory (see SORT_AREA_SIZE initialisation parameter), *space will be allocated in a temporary tablespace for doing the sort operation*."
Regards - Don Lewis

Undo and redo optimal sizes

Hi,
I need to find an optimal size of a undo tablespace and redo log files... we are designing a new database as per the formulas that are given in many websites is "UndoSpace = [UR * (UPS * DBS)] + (DBS * 24)" .... but we still didn't build the database and not sure of those values... so how to design in that cases...
Please help us at earliest..
Regards,
Ramu

Ramu Jagini wrote:
Hi,
I need to find an optimal size of a undo tablespace and redo log files... we are designing a new database as per the formulas that are given in many websites is "UndoSpace = [UR * (UPS * DBS)] + (DBS * 24)" .... but we still didn't build the database and not sure of those values... so how to design in that cases...
Please help us at earliest..
Regards,
RamuYou can only find it by empirical testing unless you know those values, which you can only find by empirical testing. The variance from certain feature usage alone can be orders of magnitude, and besides that programming style has a huge influence, as does actual user load. Beyond that, rare operations like massive loads and end of cycle processing may have much different needs. Tom Kyte makes a good case for saying you should leave large undo around for those cases, "wasted" disk is much cheaper than dealing with the lack of undo at critical times. Since you can tune redo log switching with timeouts, you might as well have redo sized for the rare cases too. You have to load the test data anyways, so that's a good first cut.
Once you have a reasonable test going you can get advice from the db. Requirements can change over time, too.

Adobe SendNow - What is the optimal size for custom logos?

I just tried to upload a custom logo (800x200) and it seemed to be stuck up in the top left corner, with a large amount of blank white screen.
What is the optimal size for this please, and how do I centre a smaller logo?
It is of course entirely possible I will need to make one in PS - not a problem - but the right sizes would be helpful info please.
Many Thanks

That is what I read too - but when I uploaded one it got tucked up in the top left corner of the "custom" setup thumbnail.
Perhaps it is just a glitch in that dialogue, but it certainly looked as if there was a raft of space to the right & underneath.
Still, probably Pilot Error so I will recheck - thank you Dave.

Optimal size of photos to import into T3

If I use 2x3 x 75 DPI the picture does not take up the whole screen. If I use an 8x10 it takes up too much memory and is slow. There must be an optimal size.
Thanks,
AlexP
Post relates to: Tungsten T3

Hello!
The Tungsten T3 has a 320x480 res LCD screen so optional resolution is 320x480, this does equate to a 2/3-3/2 aspect ratio. The 2x3 x75dpi aspect yields 150x225 resolution thus too small and 8x10 x75dpi aspect yeilds 600x750 resolution which is too big for the screen to fit. Using mspaint should give you the ability to set the resolution for both x and y axis or if you are using a more complex app use the 2/3 ratio with 120-150 DPI setting.
Post relates to: Treo 650 (Unlocked GSM)

Optimal size of System - Tablespace

What is the optimal size for the system-tablespace with all option (with JVM and more) with the ORACLE Version 8.1.7 or 9i ?

There is no one-size-fits-all answer. The options you mentioned will have some affect on the size, only because they will add more OBJECTS to the database. The key drivers for how to size SYSTEM are the number of objects and users you anticipate in your database, and the number of database structures (tablespaces, files, logs, etc). The dictionary tables in the SYSTEM tablespace exist to maintain information on everything in the database, and are updated automatically as changes are made to database objects or structures. I usually recommend 200M as a safe starting value unless you know you will be creating a lot of objects, go with 250-300M.
A little story. A while back, I was forced (while protesting quite loudly) to create private synonyms for every table in the database for every user in the database. I warned the people who ordered this that we might encounter problems in SYSTEM, (and in the shared pool) because the total number of OBJECTS (synonyms) being added totalled well over 1 million. As predicted, the system tablespace could not handle the load, and I had to add one new file to SYSTEM, and then another on a DIFFERENT storage volume (no space left on original). When this was done, our SYSTEM tablespace was almost 600M. (The OBJ$ table swelled up like a balloon). When the geniuses who forced me to do this realized it was a really bad idea, they told me to drop the synonyms. But we were left with 3 SYSTEM datafiles when we only needed one (you can't drop them).

OPTIMAL size for rollback segment in Oracle 8i

In our Database we have 13 Rollback segments & total size of all rollback segments is 33gb.
Used % it is showing 99.84%.
each rollback segment having near around 4gb of size.
I am in confusion to set OPTIMAL value for each rollback
segment.
can any one help me out reg this.
My roll back seg statistics are as fallows:
SEGMENT_NAME TABLESPACE_NAME WAITS SHRINKS WRAPS STATUS
R00 SYSTEM 0 0 12 ONLINE
RBS0 RBS 0 0 19 ONLINE
RBS01 RBS 0 0 16 ONLINE
RBS02 RBS 1 0 12 ONLINE
RBS03 RBS 0 0 11 ONLINE
RBS04 RBS 0 0 21 ONLINE
RBS05 RBS 1 0 22 ONLINE
RBS06 RBS 0 0 16 ONLINE
RBS07 RBS 0 0 15 ONLINE
RBS08 RBS 0 0 12 ONLINE
RBS09 RBS 1 0 19 ONLINE
SEGMENT_NAME TABLESPACE_NAME WAITS SHRINKS WRAPS STATUS
RBS12 RBS 0 0 13 ONLINE
RBS13 RBS 0 0 18 ONLINE
SYSTEM SYSTEM 0 0 0 ONLINE

Aman,
Definitely that would be a great approach to share the knowledge; but right now my notes are still in the shape of notes only; i have'nt tested them. I simply read forum and asktom and whenever i found good lines i copy and paste them and whenever i found the similar question in the forum i paste / repharase there in my own language and understanding (because till then i have tested and learnt them very well.)
Although i am highly obliged by your suggestation; let me that much knowledgable; so that i may run my own blog...!
Regards
Girish Sharma

Choosing an optimal size ( file size, MB's,tiff or jpg) for iphoto

I apologize to Old toad and others who have responded. OT seems to be the only one who answers so much. He deserves a standing ovation which i am giving him now.
But:
Lets start at the beginning. I am a semi-pro (i do not make my living on my photography) who never used Iphoto but must now because i wish to create a 100 page book.
I have files mostly tiffs that range from 17.2 to 60 MBs in size ( 3008-5000 /2000-3000 dpi ). I see that Iphoto ad nauseum creates a thumbnail, and a copy of the original photo for each photo. This is not HD friendly.
How big in pixel size/file size in MB's should the files be so that i do not use so much HD space? Should i just go ahead and drag the files that i have and allow for 5-10 GB of photos to accumulate on my HD? I realize i do not need
my files so big and that is why i ask here in the forums.
I realize most of my files are non compressed tiffs,i.e. big in file size.
What say you? Please be specific. Mention a specific file
size in MB's please
thanks

Glen:
I've created several books. They were with cameras that produced 1600 x 1200 pixel image files which will give a maximum 300 dpi size of 5.3 x 4 inches. All of my books have been the Storybook theme so the one photo per page is not a full page and I've never run into the warning for low resolution. Possiblly a full 8.5 x 11 photo page would have given me a warning. For the intended use of the books I found them to be very good. My Canon camera's color profile is very close to the Apple recommended sRGB so I've calibrated my monitor with the sRGB profile. Any edits I do with Photoshop CS3 embed the sRGB profile in the resulting file.
My current camera gives me 2272 x 2704 images. Haven't ordered a book since I've started using it but am in the process of creating one right now.
It's not the MB size of the file that's important but the number of pixels in the image. For a full page photos, an image size of 3300 x 2250 would meet the optimal 300 dpi of the printing by Apple's suppliers. However, I have no doubt that my current camera's files would produce a good print at that size. That is if I got a good sharp image to start with.
So a 3300 x 2250 pixel jpg would provide just as good a print as the same sized tiff. Just keep as many pixels in the image as you can. For those good photographers that can do their cropping when they take the image that will maximize the files pixels for printing. I don't have the eye for that. But then my photos are of rapidly changing family situations and I don't have time top compose the picture.
I asked Apple about the printing and quality of materials used in the books and here's their replay:
I contacted Apple and asked for information that I could pass on. Here's the reply I received from Apple:
"Thank you for contacting the Apple Print Products Customer Service.
I understand that you would like to know the printing process that is used and the color mode the files should be in, so you can better advise users in the iPhoto forum.
iPhoto version 4 or later, allows you to import and print files through the Apple Print Product service as RGB, grayscale, or CMYK color space. JPEG files with RGB color space are recommended for best results.
While iPhoto 2 can import files of various formats, including RGB color, grayscale, and CMYK, this version requires JPEG files with RGB color space when printing photos and books.
For more information regarding iPhoto 2, please visit the following article:
iPhoto: Color, Black and White Prints Appear Garbled or Distorted
For more information regarding iPhoto 5, please visit the following article:
http://docs.info.apple.com/article.html?artnum=165501
Here are some of the technical specifications for the books, cards, and calendars. I hope this gives you an idea about their quality and form.
BOOKS
All iPhoto books are printed using acid-free paper for long-lasting image quality. The photos are printed at a high resolution (300DPI if you use iPhoto 6). There is no external modification--such as sharpening or contrast adjustment--of the photos; what you see in the application is what is printed in the book.
Hardcovers Books
The cover is hard-bound and covered in linen. You select the linen color during the book-ordering process. The hardcover books have a solid, stiff binding that is glued and crimped. The internal pages, measuring 8.5 x 11 inches, are printed on McCoy 100# Text Gloss paper stock.
Softcover Books
The softcover books come in three sizes:
- Large 8.5 x 11 inches
- Medium 6 x 8 inches
- Small 2.6 x 3.5 inches
All of the softcover books have internal pages that are printed on McCoy 100# Text Gloss paper stock. The large softcover book has a white cover (Kromekoteplus Folding Cover, 16 point) with a cutout on the front that reveals the cover-page photo in the book. The covers for the medium and small softcover books have the cover image and title printed directly on the cover. All of the softcover books have a glued binding and feature a thick cover of McCoy 100# Cover Gloss paper stock.
CARDS
All cards are printed on McCoy 120# Silk Cover paper stock. The postcards measure 4 x 6 inches, and the greeting cards measure 5 x 7inches.
CALENDARS
All calendars measure 8 x 10 inches and are printed on McCoy 100# Silk Cover paper stock.
To ensure the best print quality, we have chosen to use Kodak NexPress technology. The press uses a dry toner, which is fused to the surface of the paper. Please see NexPress' site for more information:
KODAK NEXPRESS 2500 Digital Production Color Press
I hope you find this information helpful in answering questions on the iPhoto forum."
As Apple stated, I hope this information is helpful.
Do you Twango?
TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
I've written an Automator workflow application (requires Tiger), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.
MBP 2.16Ghz; G5 Dual Core 2GHz, 2G RAM ea, 250G HD; G4 Dual 1Ghz, 1.5G RAM; Mac OS X (10.4.10) 22" LCD, 710G FW HDs, Canon: SD700IS/i850/LIDE 50, Epson R200, 30G iPod, 2G Nano

Optimal Size of still photo's in iMovie 11

I'm using iMovie 11, Aperture 3, & OS 10.6.7 and have two questions:
1. What is the best image size to use for my still-images in iMovie 11. I have all my still-images in Aperture in RAW format and will export them, but unsure how large to create the jpg's.
2. Additionally, iMovie only seems to search for still-images in either Aperture or iPhoto. I cannot find anything in Preferences that will point to a folder where these jpg's can be stored outside of these app's. My understanding is also that to create jpg's from RAW in Aperture, you have to export outside of Aperture and then import back into Aperture. Does Aperture 3 have any in app feature that will do this (this questions should probably posted with Aperture discussion!).
Thanks for your help.

Current solution to my inquiry after a session consulting with the Apple Store Genuis is that I settled on allowing iMovie 11 to reference the RAW pictures from my Aperture folders. iMovie will convert the RAW files to what seems is its default, therefore my 8MB RAW images seem to be converted to 300 to 400 kb size.

Optimal Size of Pictures for each format?

I know there is no one answer for this, but I'm trying to create Photoshop templates for myself to make using images with Muse easier to deal with while working with clients. If they are going to be changing out photos with in-browser editing, it would be good to have a specific size that fits well for the full width of each format. Ideally they could do this sizing themselves. Maybe there is a cheap program for them to re-size pics.
I'm wondering what others are doing for standard (not retina) websites as far as optimum sizes for each format for screen width photos. Love the idea that I can get 3 completely different looks! Worth the work.

Thanks. That solves my problem of clients being able to re-size. However, I would love to hear ideas about sizes for full screen width pics for the three formats. Ex: Should I have a photo at 2000 pixels for a desktop? Should I match the screen resolution? Have I missed some documentation that goes over this? If I guess too large, loading time is increase. Too small and resolution suffers. I would love for Muse admin to comment on this. I could be the only idiot that is missing the obvious. If so, let me know.

Optimal size or when to start thinking about breaking main.swf

Hi!
currently I am about 1/4 way through requirements and my
main.swf file is already 433 KB, plus one module which is 128 kb ,
is there suggestions that I can get about whats the maximum
size I should target for main file ? and when should I start
worrying?

Yes, this is a problem. My biggest module is 700Kb and I
don't understand the reasons why it grows so quickly.
And as soon as you started to worry about the size of SWF
you'd probably start looking at the of the client. This is another
sad picture - every popup could get a 5mb and thanks to garbage
collector it will not be released soon. I can see how iexplorer.exe
eats 300mb.
I just don't understand it.
Regards,
Dmitri.

Station Globals resource related question( how much it allocates / optimal size of it in system)

Hi,
I have some questions StationGlobal’s oriented:
1. Does the variables of type StationGlobal allocate equals amount of memory without reference to type?
   For example: Number/String/Boolean/Object Reference allocates equals resources:Number=String=Boolean=Object Reference=’X’ bytes)
   Or Number=’X’ bytes, String=’Y’ bytes, Boolean=’Z’ bytes?
2. Does it make the difference if I have 10 or 100 or 1000 StationGlobals variables allocated in my system regards - resources of my system and
    how the quantity of it influences(or not influences) to performance of system/Test execution?
Those questions are important, because we want to know how the quantity/type of StationGlobal’s lvariables influence to overall throughput/performance of
System (e.g. Test running).
Thank you & Best Regards
*I use LabVIEW 8.X & TestStand 3.5/4.0.1 versions only

Not so strange IMHO. You might be making a mental analogy to C data structures where nothing is abstracted and you know exactly what is happening to each byte.
However, TestStand variables are black box objects with a lot more functionality than plain C data structures. Like most such objects you create via almost any object oriented API, their exact memory usage is NOT documented.
One reason memory usage is not documented is that we need to be free to change the implementation if necessary, which would not be possible if we make guarantees about exact memory usage. Another reason it is not documented is because in most practical cases, it is not important, and we don't want to mislead people into worrying about it.
If you are allocating data structures of such vastness that it actually does matter, then the task manager is an appropriate and easy tool to use to view the approximate magnitude of memory used by the objects you create. This applies to most objects from most APIs, not just TestStand variables.

Optimal Size

Similar Messages

Maybe you are looking for