DB v8 on D3 v10.2.x

[Rick Weiser]

Hi All,

I have moved my DB Applications from QM to D3 (reasons are multiple I will discuss off line if someone wants).  Anyway, I am having speed issues using D3 on a VM Server.  Its very slow on each click.  I don't think it is as other server operations are fast.

Has anyone had issues with speed on D3 v10.2.2 or above?  If so, what did you do to solve these?

Thanks,

Rick

[Dick Thiot]

Is the D3 Linux or Windows?  What is the VM platform?  VMware or HyperV or other?

--
You received this message because you are subscribed to the Google Groups "DesignBais-Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to designbais-for...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/designbais-forum/dd8efc28-ba5c-4fe9-8718-d05a06b1b590%40googlegroups.com.

[David Knight]

Hi Rick,

On the contrary, I have found it to be blindingly fast...

The only time I ever had speed issues, required me to look at each step in the chain, and the issue ended up being the time it took the browser client to render the form.

All of the other steps were blisteringly fast.

I use Windows for the server, and it all sits on the one server, that is d3/win, IIS etc is in the one VM...

You may want to try and break down the testing so as to see exactly where the issue is, time-wise?

D

[Jay]

Other tips for speedier performance are to install DB on your C:\ and D3 on the D:\ (raids help even more), set your VME size >400 MB (defaults to 256 MB) and increase the Windows paging memory size (I'm assuming you are running D3 on Windows).  On the D3 side, check to make sure that your file sizes are not undersized.

Although, I agree with David, in that most of my bottlenecks come from loading large amounts of data to the pages.

[Jay]

I realize the virtual machines manage drives differently so where you install DB and D3 may not matter.

[Rick Weiser]

Hi All,

Thanks for the reply.  I don't think its the DB app.  I load the same app on a Window 7 PC running D3 10.2.2 and its very fast.  So, there has to be some setup in VMWare that I am not setting correctly.

Rick

[David Knight]

Hi Rick,

I know you know your stuff, but for the purposes of helping us, can we be positive not only we are comparing applues with apples, but some silly thing has not been overlooked....

For example, and others have asked...

Same v of d3, that is BOTH are Windows?

File sizing identical?

Now I am assuming those things to be identical, in which case you should be able to do some testing to find out where the bottleneck is... For example build a really simple CRUD form, no select, just a direct read with a few fields populated.

How does that behave? Use the various tools built into the various layers to see where the performance hits are occuring... is it d3 on the vm? Is it IIS on the vm??

Unfortunately, I am NOT an expert, nor even remotely one on VMWARE; but I do believe from conversations I've had with IT staff who setup these things that a LOT depends on the power of the underlying hardware and how many VM's there are on the real hardware. Perhaps that is something to look at? Secondly, remembering I am NOT an expert, I "think" the VM can have resources statically made available, or dynamically made available. For something like d3/win; which by definition is itself a VM, it would NOT take too kindly to having it's resources allocated dynamically, since the resources it wants would need to be available instantly. Presumably not giving the VMWARE software enough time to work out that resource demand just spiked; for the spikes are far too short. Total guess, but may point you in a direction to start playing with parameters to see what makes/breaks the problem.

Good luck!

[Rick Weiser]

While I would normally agree with you David, the problem is not the app or the file sizes.  This problem shows up in the developer.  Simply clicking the Forms Design menu option takes > 4 seconds.

[David Knight]

Oh! Missed that important point.

So do this happen in ALL of the tools, mind you FD is pretty much everything. What about the Selection tool?

As you know, these tools are basically "built" in db itself insofar as they have subroutines that fire up on load etc... So, I would still be looking to find if the system is slow everywhere, or only when doing certain things like running the s/r as part of FD.

That may assist in isolating if this is an overall issue of just with the tools.

For example, at good 'ol TCL run some big sorts etc and see if d3 itself is having a performance issue.

Like I said before, create and run a really simplistic CRUD form and run that [not within FD, actually run it] etc, and build up concepts of what does and does not work and be affected.

That may give you a clue if the issue is

CPU bound.

Memory Bound
Timeslice bound.

Then that may give you a clue as the likely setting which needs changing.

HTH