64 bit vs 32 bit Labview on an AMD Opteron 6380

When running my code on an AMD Opteron 6380 processor, Labview 2014 64bit runs 4 times slower than when running with Labview 2014 32bit.  However the same code running on and INTEL Core i7 ran twice as fast with Labview 64bit vs 32bit.  Does anyone know why?  Note that the code is math intensive running a parallel loop that does not cummunicate with the outside world, i.e. no file access, property nodes, etc.Thank you.

Yes the 6380 FPU is shared between two cores.  I just ran a diagnostic I made up that generates an array of 1 million random numbers, takes the average of those, and then excutes that repeatedly in a parallel loop.  The 6380 showed a 20% to 30% improvement in speed between LV64 & LV32 bit depending on how many cores I told it to use.  So that seems to make more sense.  The other code that I was running that ran 4 times slower has a complicated clusters within a cluster structure including a large look up table array that is being passed around amoung several vi's.  If it is moving that large amount of data around in memory, instead of just the pointer, that might explain it.  But why then would the AMD run slower with 64 bit (by a factor of 4) when compared with the Core i7 which ran twice as fast, which kind of makes sense to me if it is moving that data around with twice the bandwidth?

Similar Messages

  • Oracle (9.2.0.2.1) for 64-Bit Windows Compatibility with AMD Opteron 64 bit

    Dear all:
    please advice is AMD Opteron 64 bit compatible with oracle version (9.2.0.2.1) for 64-Bit Windows .

    Help yourself :
    http://www.oracle.com/technology/support/metalink/index.html
    Nicolas.

  • Can I run 64 bit LabVIEW and 32 bit LabVIEW on the same machine?

    If I have a 64 bit OS (Windows 7 64 bit or Server 2008 64 bit) can I install and run 32 and 64 bit LabVIEW on the same machine?
    John

    LabVIEW 64-Bit vs. 32-Bit Applications FAQ
    Q. Can I have both LabVIEW 32-bit and LabVIEW 64-bit installed on the same 64-bit machine?
    A. Yes.
    The FAQ will likely answer other questions you have regarding the restrictions and issues you will have with having both versions and compiling in one vs the other.

  • Calling 64-bit TestStand Engine from 32-bit LabVIEW

    I am creating my own TestStand user interface in 32-bit LabVIEW but I want to use the 64-bit TestStand Engine. I can't find a way to specify this. The read-only API property "Engine.Is64Bit" is coming back false when I run from my UI, but when I run from the Sequence editor, it comes back true.  How is this determined and set at startup???

    I dont think you can build a 64 bit TestStand interface using a 32 bit Labview.
    FYI the the 32 bit User interface code is stored at :
    C:\Users\Public\Documents\National Instruments\TestStand 2014 (32-bit)\UserInterfaces\Full-Featured\LabVIEW
    The 64 bit user interface code is stored at :
    C:\Users\Public\Documents\National Instruments\TestStand 2014 (64-bit)\UserInterfaces\Full-Featured\LabVIEW
    You have build a 32 bit TestStand user interface and the is64bit is properly showing as false.
    Try building the same project using 64 bit Labview (which should automatically pickup 64 bit TestStand components)
    When you say that you run from seqeunce editor - i think you mean 64 bit sequence editor.
    Ofcourse once you build your 64 bit user interface you can call a 32 bit vi (only in adapter mode set to dev and not run time).
    Hope this helps.
    Ravi

  • Use of APT objects in 64-bit LabVIEW

    I have created an APT motion control VI to control a translation stage using 32-bit LabVIEW. However, I have since had to move to 64-bit LabVIEW. I am trying to create a similar VI that will run on the 64-bit version. The problem is when I create my ActiveX container and try to use MGMotor control to connect to the motor, MGMotor Control is not in my list of creatable objects.
    Is this because it is not possible to access this particular motor in 64-bit LabVIEW or am I missing drivers that I can download to update the list of creatable objects?
    P.S. I am relatively new to LabVIEW but any help at all would be great!

    Hi,
    What is the reason you have moved to 64bit LabVIEW? It could be that this driver is not supported on 64 bit LabVIEW but this would have to be confirmed by looking at the driver's requirements.  64 bit LabVIEW currently does not support every thing that 32 bit does but this is being worked on.  Can you provide some more details of this motor driver.
    If you have recently installed your new version of LabVIEW then you will need to reinstall the driver again. If you can provide some more details on the driver then perhaps we can find out if it is compatible with 64 bit LabVIEW
    Best regards
    Matt Surridge
    National Instruments

  • Using access with 64 bit labview

    Hello,
    I have 64 bit version of Labview, and I want to use an access database.  I used the internal search for examples, and it showed an example in examples/comm/access.llb.   Well, that does not exist with this install.  (I did a 32 bit install, and they exist.)
    Has anyone have success with 64 bit LV and access?   Any links to where to start...  Just need a nudge in the right direction.  
    -- brett

    Thanks for that suggestion Ian.
    I've looked through our documentation on 64-bit compatibility for LabVIEW and it looks like you are correct, that should not have installed. What I didn't realize was that the test machine I was using also had 32-bit labview, so the example finder located all of those examples.
    Is there any reason you cannot use the 32-bit version of LabVIEW? At the moment, that is the best option we have for internal compatibility, as most toolkits have not been ported to the 64-bit version of LabVIEW, even though they can run on a 64-bit operating system.
    Past that, I've taken a look at Ian's suggestion and it seems like a pretty solid thing to try, along with the API in the second post of that thread.. Let us know if it works for you.

  • MATLAB DataPlugin for 64-bit LabVIEW

    Where is the 64-bit LabVIEW support for writing Matlab .mat files?  Or is the source code available for the 32-bit version (http://zone.ni.com/devzone/cda/epd/p/id/4178) so that someone can compile their own?
    Thanks,
    D

    To clarify what Chris said, 64-Bit Operating Systems with a 32-Bit emulation (x86 directory) are certainly fine with 32-Bit LabVIEW. (this excludes Windows XP 64-Bit as it has no emulation layer)
    Most general 32-Bit vs. 64-Bit LabVIEW questions are covered in this KnowledgeBase article.
    To summarize, you'll have full LabVIEW functionality with the 32-Bit version.
    The 64-Bit version of LabVIEW is really only recommended for Vision applications that need the additional resources for large image processing. 
    As another note, currently, most of our software also only supports 32-Bit versions of The MathWorks, Inc. Software.  
    MATLAB® is a registered trademark of The MathWorks, Inc.
    Applications Engineer
    National Instruments
    CLD Certified

  • No 64-bit long ints in LabVIEW 7? [Also: beta version of 64-bit LabVIEW?]

    Is there no primitive data type in LabVIEW 7 that corresponds to a 64-bit long int? [I guess LabVIEW would call it either I64 or U64...]
    Please, please tell me I'm wrong - if I'm right, this is an unacceptable state of affairs.
    And, if I'm right - when will LabVIEW be upgraded to 64-bit-ness? Is there a beta version of 64-bit LabVIEW out there that I could get involved with? [I'd really, really like a 'for' loop that could take 64-bit ints as its counters.]
    Anyone know anything about this?
    Thanks!

    There is no native support for 64 bit ints. I don't expect to see that until Windows has support for 64 bits. For work arounds, see this posting.

  • 64-bit Labview 2013 Ni-845x = ?????

    Rediculous....
    If I have the following setup:
    - Windows 7 64-bit
    - Labview 2013 64-bit
    - NI USB-8452
    What driver do I use??????? 
    v2.1.2 is 32-bit only...
    v2.1 coverd 64-bits but not for Labview 2013, stops at 2012. Found this in a random compatibility chart no where near the damn driver or HW pages. 
    This is a maze of information, and digging for info like this should not be the norm.
    My NI USB-8452 is glitchy when looking for it in NI Max. When I try to use the driver for I2C setup and immediately disconnects from USB (I hear the Window USB disconnect noise).
    Has anyone had this problem? What driver do I use for Labview 2013 64-bit  for the NI USB-8452.

    My box is still not working. 
    I have:
    NI USB-8451 (works fine)
    NI USB-8452 (fails on ARG1 and I know it is right).
    How can the same piece of cod work for one and not the other. It work previously, and now all of the sudden it's broken for the 8452 only.
    See attached picture.
    Please help me before I go insane.
    Attachments:
    WTF.png ‏19 KB

  • A source distribution created in 32-bit LabView 2009 says that VIs aren't executable when opened in 64-bit LabView 2009. How do I run the main VIs?

     A source distribution was made for a VI using 32-bit LabView 2009. The distribution was verified to work on another machine that ran 32-bit LabView 2009. However, when opened on a 64-bit LabView 2009, the VI was broken as indicated by the attached error message. How do I make the VI executable?
    Solved!
    Go to Solution.
    Attachments:
    source dist error.JPG ‏70 KB

    Seems you have a problem with the installation of the Advanced Analysis Library (AAL) or the Intel Math Kernel Library that is used by the AAL on that 64 bit machine. Can't say for sure if these are already supported on 64 bit LabVIEW. At least a repair installation of LabVIEW seems to be in place.
    The other error is from the HSD component not working. Again I can't say if this should even work on 64 bit LabVIEW. If it should a repair installation should be most probably done.
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • NI-RIO 4.0 not compatible with 64-bit LabVIEW?

    Hi,
      I have a 7841R multifunction RIO card.  I'm currently installing the evaluation version of LabVIEW to test it out.  I've got 64-bit LabVIEW successfully installed and I had installed NI-RIO 3.6 (which was on the disk that came with the card).  In the process of installing other features (I believe the C interface for FPGA or something) I discovered that I needed NI-RIO 4.0.  I uninstalled NI-RIO 3.6, downloaded NI-RIO 4.0 and now I'm attempting to install it.  I get the following message a few steps into the process:
    Important note about NI-RIO support for LabVIEW (64-bit Versions)
    A 64-bit version of LabVIEW was detected on your system.  This version of the NI-RIO driver does not support 64-bit versions of LabVIEW.  However, this version of NI-RIO is fully compatible with 32-bit versions of LabVIEW installed on 64-bit operating systems.
    Is there a version of NI-RIO 4.0 that supports 64-bit versions of LabVIEW?  If so, could you point me to it?
    Or should I install the 32-bit version of LabVIEW?
    Thanks for the help!
    Cheers,
    tom
    Solved!
    Go to Solution.

    Hey Tom,
    Unfortunately we do not have a RIO driver that is compatible with our 64-bit LabVIEW Development software.  If you need to use the RIO driver, you should install the 32-bit version of LabVIEW and build your applications in that development system.  Sorry for the confusion initially during the installation process!
    Ben N.
    Applications Engineering
    Certified LabVIEW Developer

  • Mathscript node: an internal mathscript error has occurred: 64-bit LabVIEW 2009

    Hi Folks -
    I have an installation now of
    LabVIEW 2009 9.03f, Vision, and Advanced Signal Processing Toolkit, all
    64-bit versions on a new computer so that I can convert some code from
    32- to 64-bit.
    I figure I will address errors
    one-by-one and here's the first one.  I have a VI with a mathscript
    node and the VI, which loaded and ran fine in the 32-bit environment,
    is now broken and giving the error "mathscript node: an internal
    mathscript error has occurred."  My main concern - is mathscript not
    supported in 64-bit LabVIEW right now?
    I am attaching the VI.  Any ideas are appreciated.  I need to get this working.
    Also, NI, is there a special 64-bit forum that we should post to in the future, or create to post to?
    Sincerely,
    Don 
    Solved!
    Go to Solution.
    Attachments:
    sort.vi ‏753 KB

    From 2009 help
    LabVIEW MathScript is a text-based language you can use to write functions and scripts. You can process scripts using LabVIEW MathScript in the LabVIEW MathScript Window or a MathScript Node. When you create a LabVIEW MathScript, you must use supported data types.
    The MathScript syntax is an intuitive and logical
    syntax predominantly based on standard mathematical and computer
    programming terms, terms in widespread and common use, and/or
    descriptive abbreviations, truncations and concatenations of standard
    terms. The LabVIEW MathScript Window and MathScript
    Nodes are able to process files you create using the current MathScript
    syntax and, for backwards compatibility, files you created using legacy
    MathScript syntaxes. The LabVIEW MathScript Window
    and MathScript Nodes also can process certain of your files that use
    other text-based syntaxes, such as files you created using the MATLAB® software. Because the MathScript RT Module engine is used to process scripts in the LabVIEW MathScript Window
    and MathScript Nodes, and because the MathScript RT Module engine does
    not support all syntaxes, not all existing text-based scripts are
    supported.
    (LabVIEW 64-bit) LabVIEW MathScript is not supported in LabVIEW (64-bit).

  • 64-bit LabVIEW - still major problems with large data sets

    Hi Folks -
    I have LabVIEW 2009 64-bit version running on a Win7 64-bit OS with Intel Xeon dual quad core processor, 16 gbyte RAM.  With the release of this 64-bit version of LabVIEW, I expected to easily be able to handle x-ray computed tomography data sets in the 2 and 3-gbyte range in RAM since we now have access to all of the available RAM.  But I am having major problems - sluggish (and stoppage) operation of the program, inability to perform certain operations, etc.
    Here is how I store the 3-D data that consists of a series of images. I store each of my 2d images in a cluster, and then have the entire image series as an array of these clusters.  I then store this entire array of clusters in a queue which I regularly access using 'Preview Queue' and then operate on the image set, subsets of the images, or single images.
    Then enqueue:
    I remember talking to LabVIEW R&D years ago that this was a good way to do things because it allowed non-contiguous access to memory (versus contigous access that would be required if I stored my image series as 3-D array without the clusters) (R&D - this is what I remember, please correct if wrong).
    Because I am experiencing tremendous slowness in the program after these large data sets are loaded, and I think disk access as well to obtain memory beyond 16 gbytes, I am wondering if I need to use a different storage strategy that will allow seamless program operation while still using RAM storage (do not want to have to recall images from disk).
    I have other CT imaging programs that are running very well with these large data sets.
    This is a critical issue for me as I move forward with LabVIEW in this application.   I would like to work with LabVIEW R&D to solve this issue.  I am wondering if I should be thinking about establishing say, 10 queues, instead of 1, to address this.  It would mean a major program rewrite.
    Sincerely,
    Don

    First, I want to add that this strategy works reasonably well for data sets in the 600 - 700 mbyte range with the 64-bit LabVIEW. 
    With LabVIEW 32-bit, I00 - 200 mbyte sets were about the limit before I experienced problems.
    So I definitely noticed an improvement.
    I use the queuing strategy to move this large amount of data in RAM.   We could have used other means such a LV2 globals.  But the idea of clustering the 2-d array (image) and then having a series of those clustered arrays in an array (to see the final structure I showed in my diagram) versus using a 3-D array I believe even allowed me to get this far using RAM instead of recalling the images from disk.
    I am sure data copies are being made - yes, the memory is ballooning to 15 gbyte.  I probably need to have someone examine this code while I am explaining things to them live.  This is a very large application, and a significant amount of time would be required to simplify it, and that might not allow us to duplicate the problem.  In some of my applications, I use the in-place structure for indexing
    data out of arrays to minimize data copies.  I expect I might have to
    consider this strategy now here as well.  Just a thought.
    What I can do is send someone (in US) via large file transfer a 1.3 - 2.7 gbyte set of image data - and see how they would best advise on storing and extracting the images using RAM, how best to optimize the RAM usage, and not make data copies.  The operations that I apply on the images are irrelevant.  It is the storage, movement, and extractions that are causing the problems.  I can also show a screen shot(s) of how I extract the images (but I have major problems even before I get to that point),
    Can someone else comment on how data value references may help here, or how they have helped in one of their applications?  Would the use of this eliminate copies?   I currently have to wait for 64-bit version of the Advanced Signal Processing Toolkit for LabVIEW 2010 before I can move to LabVIEW 2010.
    Don

  • Random crashes when using 16 Labview with the 32 bit labview

    I am using 2 versions of Labview at the same time, one is version 4 which has a camera and a weigh-in-motion scale attached to it. The second is either Labview version 4, 16-bit or Labview 3.0.1, 16-bit, i'm not sure. The sixteen bit has a data acquisition system attached to it. Its an optim electronics system and the 16-bit Labview drivers for the optim were provided by Optim electronics and so I am stuck with using the same system. When I use both these systems in tandem, the system crashes frequently, but both systems run fine independently. It usually just freezes up or says "Illegal operation performed. Contact program vendor". Its a windows error with a red cross.

    So a guy goes into his doctors office and tells his doctor "Ya gotta
    help me doc...it hurts when I run my head into the door like
    this...OW!". Then the doctor says:
    "DON'T DO THAT ANY MORE!!!"
    (I promise to keep my day job...oops what job...and not go into
    comedy..)
    Why don't you convert all the old 16 bit code into 32 bit code and
    create one application where the various parts all know about each
    other? I don't think that there's any way to coordinate an old 16 bit
    LV and a new 32 bit LV application so that they don't step on each
    other driverwise like they appear to be doing. I don't think that the
    two LabVIEW's even know that the other exists!
    Alternatively, get a second computer to run the 16 bit code on and
    make the two apps communicate with
    each other using TCP/IP or serial.
    Doug De Clue
    [email protected]
    cincidude wrote in message news:<[email protected]>...
    > I am using 2 versions of Labview at the same time, one is version 4
    > which has a camera and a weigh-in-motion scale attached to it. The
    > second is either Labview version 4, 16-bit or Labview 3.0.1, 16-bit,
    > i'm not sure. The sixteen bit has a data acquisition system attached
    > to it. Its an optim electronics system and the 16-bit Labview drivers
    > for the optim were provided by Optim electronics and so I am stuck
    > with using the same system. When I use both these systems in tandem,
    > the system crashes frequently, but both systems run fine
    > independently. It usually just freezes up or says "Illegal operation
    > performed. Contact program vendor". Its a windows error with a red
    > cross.

  • Win\32\nodemanager.dll:Can't load IA 32-bit .dll on a AMD 64-bit platform, while installing OIM.

    Hi All,
    I have installed Weblogic server with default domain. That installation was successful but when I started the OIM(Oracle Identity Management) set-up it halted at configuration step: "Create Domain"
    I found the below logs under "C:\Oracle\Middleware\WebLogic\wlserver_12.1\common\nodemanager"
    weblogic.nodemanager.common.ConfigException: Native version is enabled but nodemanager native library could not be loaded
        at weblogic.nodemanager.server.NMServerConfig.initProcessControl(NMServerConfig.java:269)
        at weblogic.nodemanager.server.NMServerConfig.<init>(NMServerConfig.java:210)
        at weblogic.nodemanager.server.NMServer.init(NMServer.java:183)
        at weblogic.nodemanager.server.NMServer.<init>(NMServer.java:149)
        at weblogic.nodemanager.server.NMServer.main(NMServer.java:373)
        at weblogic.NodeManager.main(NodeManager.java:31)
    Caused by: java.lang.UnsatisfiedLinkError: C:\Oracle\Middleware\WebLogic\wlserver_12.1\server\native\win\32\nodemanager.dll: Can't load IA 32-bit .dll on a AMD 64-bit platform
        at java.lang.ClassLoader$NativeLibrary.load(Native Method)
        at java.lang.ClassLoader.loadLibrary1(ClassLoader.java:1939)
        at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1864)
        at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1854)
        at java.lang.Runtime.loadLibrary0(Runtime.java:845)
        at java.lang.System.loadLibrary(System.java:1084)
        at weblogic.nodemanager.util.WindowsProcessControl.<init>(WindowsProcessControl.java:17)
        at weblogic.nodemanager.util.ProcessControlFactory.getProcessControl(ProcessControlFactory.java:24)
        at weblogic.nodemanager.server.NMServerConfig.initProcessControl(NMServerConfig.java:267)
        ... 5 more
    Although I have installed Weblogic using 64-bit JVM rather than using it's default JDK.
    Can anyone help me?

    Thanks for the quick reply Chris.
    You're right. When I run file libttclient.so on the different client files, I see the version 5 one is 64-bit but the version 6 one is 32-bit.
    Version 5 fie: libttclient.so: ELF 64-bit LSB shared object, AMD x86-64, version 1 (SYSV), not stripped
    Version 6 file: libttclient.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), not stripped
    The SysAdmin says they don't have 64-bit versions. Oh dear! And the developers aren't keen on changing their code to use a 32-bit JVM.
    Ah well, thanks for the response.
    Best wishes!

Maybe you are looking for

  • Is there a way to specify a number of vlookup results?

    I'm trying to make a kind of loose pivot-table-like date record lookup. Probably best if I show something analogous to what I'm wanting: Table1 Date BookRead 1/1/13 Les Miserables 1/2/13 The Hunchback of Notre Dame 1/3/13 Les Miserables 1/4/13 The Ph

  • It will not save as a jpeg from a bmp

    I found info on how to save a .bmp to a .jpeg (thank you) but when I went to save it as it says..the computer said that "this document could not be saved as...." Why? I scanned the printed pictures at a store they were then transfered onto a CD. I pu

  • Does Muse support multiple renditions of the same site?

    I have built a desktop website, but would also like to build a mobile version of the same site. Can Muse support a desktop and mobile edition of the same website? So for example, if the user is viewing the site on an iPhone, they see a mobile-optimis

  • Suddenly can't save any adobe products in a root folder

    can only save adobe documents (indesign, illustrator, photoshop) in a main folder and not able to save into a sub folder.  thoughts?

  • Need to RMA my 7900gt

    So I've been putting up with on and off artifacting on my MSI 7900gt for around 6-8 months now, however the card has basically become unusable, with colored and misspelled text on boot screen, huge colored shapes, flashing and colored specs on the de