All questions related to 1C:Enterprise licenses

#1
People who like this: 0 Yes / 0 No
Just came
Rating: 1
Joined: May 8, 2018
Company: Profsis Yazılım Ltd. Şti.

What are the differences between the products below.
but a 32 bit system can be installed on a 64 bit system.


4601546102027 1С:Enterprise 8. Server license (x86-32)
4601546102034 1С:Enterprise 8. Server license (x86-64)

 
#2
People who like this: 0 Yes / 0 No
Interested
Rating: 16
Joined: Dec 4, 2017
Company:

Dear harun Fişekci,

The main difference between the x86-32 and x86-64 versions of 1С:Enterprise 8 Server is the size of the accessible memory address space. For each working process, an x86-32 server can access up to 2GB of the memory address space. An x86-64 server does not have such a limitation.

As a result, an x86-64 server has the following advantages over an x86-32 server:

- Larger scalability limit
An x86-64 server withstands a larger system workload increase, like an increase in the number of concurrent users or in the number of resource-consuming procedures running at the moment.

- Longer uptime
In certain workload scenarios, an x86-32 server may require rebooting periodically to rule out the memory fragmentation effect. An x86-64 server can work without rebooting during practically unlimited periods of time.

- Better RAM utilization
Each working process of an x86-32 server can access up to 2GB of the memory address space. If the computer where the server is deployed has a larger memory address space, then, to utilize it efficiently, you have to create several working processes. An x86-64 server can access a practically unlimited memory address space via a single working process.

Best regards,
Vladimir Gurov

1C Company support team
 
Subscribe
Users browsing this topic (guests: 1, registered: 0, hidden: 0)
Be the first to know tips & tricks on business application development!

A confirmation e-mail has been sent to the e-mail address you provided .

Click the link in the e-mail to confirm and activate the subscription.

/* Улучшаем читаемость списков в документации */ .workarea ul, .content ul { margin: 15px 0 20px 25px !important; padding: 0 !important; list-style-type: disc !important; } .workarea li, .content li { margin-bottom: 8px !important; padding-left: 5px !important; line-height: 1.6 !important; } /* Ультимативный фикс для всех уровней заголовков в контенте */ .workarea h1, .workarea h2, .workarea h3, .workarea h4, .workarea h5, .workarea h6, .content h1, .content h2, .content h3, .content h4, .content h5, .content h6, div[id*="content"] h5, div[class*="content"] h5 { display: block !important; font-weight: 700 !important; color: #005aa0 !important; /* Наш фирменный синий */ text-transform: none !important; margin-top: 30px !important; margin-bottom: 15px !important; line-height: 1.2 !important; font-family: Arial, sans-serif !important; } /* Принудительные размеры в пикселях (чтобы не зависеть от % или em) */ .workarea h1, .content h1 { font-size: 28px !important; } .workarea h2, .content h2 { font-size: 24px !important; } .workarea h3, .content h3 { font-size: 21px !important; } .workarea h4, .content h4 { font-size: 19px !important; } .workarea h5, .content h5 { font-size: 18px !important; } /* Для 5 решеток ##### */ .workarea h6, .content h6 { font-size: 16px !important; } /* Фикс, если Битрикс добавил лишние отступы перед списками после заголовка */ .workarea h5 + ul, .content h5 + ul { margin-top: 5px !important; }