Under Community Review

64-bit version of Studio

Please create a 64-bit version of Studio. At present only a 32-bit version is available, and therefore it can theoretically only access 2-3GB of system memory, meaning that upgrading your machine with more memory then this does not have any beneficial impact on Studio performance.

When handling large files & projects, allowing Studio access to all of your system's memory would make a huge difference in time and performance, and for this the app needs to be 64-bit.

Are there any plans to release a 64-bit version in future?

Jay Young
Parents

  • This is over 5 years old. Why is it still even in question? I have 32 GB of RAM, most of which Trados can't access. I do huge projects in MemoQ.

  • in reply to Neil Allen

    Moving a 32-bit application to 64-bit can offer several benefits such as increased memory access and improved performance. However, if the underlying code has problems that prevent it from being effective, simply moving the application to 64-bit will not solve those issues. In fact, it may even exacerbate them.  Moving a 32-bit application to 64-bit can offer benefits, but it is not a solution to underlying code problems. To fully take advantage of a 64-bit system, the code must be optimized and designed to handle the larger memory address space and other features of a 64-bit architecture.  This work is being carried out on a regular basis and being properly able to support 64-bit is a goal for us as well.

  • in reply to Paul

    I agree, which is obviously why it has not been done. Otherwise, it would just be a compiler setting. I suspect that the entire code of Studio, and its libraries and dependencies, needs refactoring, which may be a prohibitively expensive job.

  • in reply to Paul

    I think you have lost the original developers and the current ones are hopelessly overstretched. One gets the impression that they are just poking around in the code to be able to charge money for a new update.

  • in reply to Neil Allen

    It is work that has been ongoing and considerable progress has been made.  Unfortunately it's work nobody sees so users understandably get the impression we're doing nothing, but every single release has done something towards it.  There are always competing priorities but the development team are doing their best to deliver on them all and we will get there.

  • in reply to Paul

    I understand and I do appreciate the efforts being made. The comments I have made were entirely in the spirit of constructive criticism to improve a tool which, despite all the competition, still has many assets not matched elsewhere.

  • in reply to Paul

    Hi Paul,

    Trados crashes with a System.OutOfMemoryException when trying to import a very large XML file (108MB). Trados crashes when it hits 2.5-3 GB of ram usage while adding the file to the project (we can see this with Windows' Task Manager). Moving to 64 bit would obviously solve this problem, as our PCs have a lot of ram installed, which Trados can't currently take advantage of.

    We had to resort to splitting up the XML file in several chunks, which is error-prone and far from ideal.

    So please elevate the priority of moving to 64 bit, as we are experiencing lack of memory-related issues more and more.

    Thanks,

Comment
  • in reply to Paul

    Hi Paul,

    Trados crashes with a System.OutOfMemoryException when trying to import a very large XML file (108MB). Trados crashes when it hits 2.5-3 GB of ram usage while adding the file to the project (we can see this with Windows' Task Manager). Moving to 64 bit would obviously solve this problem, as our PCs have a lot of ram installed, which Trados can't currently take advantage of.

    We had to resort to splitting up the XML file in several chunks, which is error-prone and far from ideal.

    So please elevate the priority of moving to 64 bit, as we are experiencing lack of memory-related issues more and more.

    Thanks,

Children
No Data