cancel
Showing results for 
Search instead for 
Did you mean: 

Language Selection in Business Packages

Former Member
0 Kudos

When loading the ESS/MSS business packages I've noticed it is building all the components for ALL countries/languages which makes our load time run for days! Is there anyway to select which languages to build (in our case just US/English) to speed up the build/deploy time?

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Jason,

simple answer: No.

Are you sure that languages are the real problem here? From what I've seen the overhead they add to the build time shouldn't be that extreme. Nearly 30 000 XLF files in bp_ess are usually processed in approximately 5 minutes and most components have much less XLF files than that. Web Dynpro generation is usually much more expensive.

Regards,

Marc

Former Member
0 Kudos

Thanks for the reply.

No, I was just speculating as to the multiple languages being the cause. We are experiencing poor performance overall and are looking for causes. Some of our other suspects are the file system partition (perhaps not set up to handle that many temporary files) or the VM constantly doing garbage collection.

Would you happen to have any other suggestions or insight on those supects?

Former Member
0 Kudos

Hi Jason,

well, that depends very much on your hardware setup and CBS configuration...

By default CBS will put all temporary files in a folder relative to the server installation (/usr/sap/.../cluster/server/CBStemp or something like that, it's configured as "rootFolder" in the CBS service properties). Depending on your hardware setup that may not be the best thing (e.g. if your engine installation is on a RAID5 partition, a fast, non-failsafe RAID0 partition is better here). If you are on a Unix system the file system used on that partition may also be relevant, Veritas on HP may need some fine-tuning but I'm no expert on that.

If the threadPoolSize is too high CBS may also run into problems as each build VM will basically starve for memory or CPU time. To eliminate side effects I'd try to set this to 1 (forcing a completely serialized build). If there are still performance problems after that then you should definitely take a look at the filesystem.

Regards,

Marc

Answers (0)