How-to optimize the SDK?

[Jacques-Antoine]

Hello SDK community,

I ask this question because since I started with the 1311 Studio release, I have big problems with the SDK. I find it very slow and I am not efficient at all as I have to wait for a long time each time I want to do something.

Actually, I find it very very very slow. I never had such a slow dev environment.

As soon as I open the UI Designer, I get the "Not responding" and it takes 1 or 2 min to open the UI Designer.

When I activate a solution, same thing, the "Not responding" and a big delay.

When I try to complete code with CTRL+J, 8 out of 10 times it just does not give me any completion suggestion, 1 out of 10 it gives it to me but it is very slow to show and 1 out of 10 it works like a charm.

When I query a BO, it takes sooooo long, even when I only have 150 records in a table. I thought the database was powered by HANA, but it does not seem to be (I know the power of HANA as it is my expertise normally). And of course, for each query, when I execute it, I have the "Not responding".

And the best thing is certainly when I connect to a repository. 3 out of 10 times, it says: "SAP Cloud App Studio is finishing a task in background. If you encounter this problem, please contact the MS Visual Studio support". Even if nothing should be running as I an the only user of the SDK in our company.

This is really a pain to be productive in such a situation.

If someone could give me some advice on how to optimize the SDK it would be a greatly appreciated help.

Config:

Lenovo X1 Carbon

8 Go RAM

Core i7 vPro

Flash SSD

Windows 8.1

Best regards.

Have a nice day everyone.

Jacques-Antoine

[Paul_Ka]

Hi,

The location of the tenant will definitely be the major factor. I have tenants in Germany and in Australia and being located in Australia the difference in speed is just massive.

But as others mentioned, there could be another issue with your tenant so it won't hurt to raise an incident.

Also, if you run trace route to your tenant check if the route goes via Akami technologies routers, it's generally faster.

Cheers,

Paul

[Former Member]

Hi,

For the solution activation problem: One thing I can suggest is to not activate the entire solution all at once until you are finally ready to activate the entire thing prior to assembling.  We have seen this problem before with large solutions that a number of users are activating the solution itself instead of their individual objects.  It doesn't sound like you have a big team based on your comments, but still activating only individual objects should speed that part up.

Michael

[Jacques-Antoine]

Hello Michael,

Yes, of course in a shared development environment, the Activation process has to be tailored.

However, I am alone on it. And even Activating a simple XBO with a Before-Save and a validation OnSave takes too long to my taste.

Actually, the worst thing for me is the repository explorer, because I use it a lot. Each time I switch of BO, it takes several seconds (almost 30s if not a minute) to display the corresponding doc. Even if I only switch field in the same BO.

But Ludger and Horst are right, performance is really depending on the tenant I am working on.

Some are slow as hell, other are quick enough that it does not bother me. And I also made some testing in the Cloud Solution to make sure it was related to tenants. And a tenant which is slow in the SDK is slow in the Cloud Solution, and vice versa.

Now the question is: why is this so random?

Because this is hard to believe that for the same product and the same licensing price, customers get different performance on tenants!

I hope this back end performance is not on SAP side, because it would be a big flaw in the pricing. Like you pay the same as you competitor but your system does not run as well.

PS: Horst Schaude, when you say contact the hosting guy, what do you mean by that? How can we know who is hosting Bydesign for our customers?

I thought every Bydesign system was hosted by SAP Germany through sub contracting, so we cannot know who is sub contracted by SAP.

Besides, I thought ByDesign was hosted at SAP Germany until the future data centers for HANA DB are deployed (I think only Germany, Philie and Shanghai are deployed for now, Canada is scheduled for December if I am not mistaking).

Than you all for your attention.

Best regards.

Jacques-Antoine

[HorstSchaude]

Hello Jacques-Antoine,

You're right if you mention that you do not / can not know whoe is responsible for the hosting.

Sorry if I was not that exact: Simply raise an incident in which you describe what happens under which conditions.

That' s your only chance.

Sorry,

    Horst

[Former Member]

same case for me

Removing a condition in the UI designer takes 5 mins...

I hope SAP is doing something about this.

[HorstSchaude]

Hello Jacques-Antoine,

This sound to me more an issue with the backend.

For example the UI Designer is installed at your local machine. What it needs for working is just the data coming from the backend.

Or take the query execution: The UIs shown in the SDK are pretty simple (Input mask, result list as table). The whole work is performed at the backend.

My suggestion: Get into contact with the hosting guy (you may even raise an incident) and tell them thaht the system is slow (with some examples)

HTH,

    Horst

PS: I agree, that there is place for the SDK to run faster, especially the assemble part.

     We are working on it.

[Former Member]

Yes, development is really slow.

We had the experience that this varies depending on the tenant you are developing on.

Our development tenant is quite ok-isch.

However our test tenant is reaaaaallly slow.

Using the tenant however seemed to speed reaction times up (a little bit). I don't know why but using the tenant seems to speed things up (slightly). Maybe SAP uses some internal performance profiling and readjust resources as they are required.

Best regards,

Ludger