Author Topic: Slickedit unusable with X forwarding  (Read 6688 times)

AxeMaster

  • Community Member
  • Posts: 13
  • Hero Points: 0
Slickedit unusable with X forwarding
« on: June 02, 2008, 06:13:28 pm »
I'm trying to use a remote Slickedit (on linux) forwarding the display to the X server on my local machine  I'm doing this through a VPN (not SSH tunnel).  My connection is "decent" -- 3mbps down/512kbps up w/ 40ms ping times.  However, when starting slickedit up, it takes about 15 minutes.  Once its up, its too slow to be usable because any mouse-overs or pop-ups make it unresponsive for a while.

Does anyone know if there is a way to turn off some of the "bling" in the UI to speed things up?  Has anyone else witnessed such behavior?  I have a suspucion that the slowness of the remote X session scales with the size of my workspace (I have 4+ projects open --  1 project is the linux kernel (~20,000 files), another projects is about 2000 files, the remaining projects are insignificant) because the UI stops painting right after it draws the workspace window and it flickers like it is being constantly refreshed.

I have a work-around for the problem -- which is running it in a vncserver.  This mode is actually pleasantly fast but doesn't integrate as nicely into my environment.

Any help would be appreciated.

-Miles

chrisant

  • Senior Community Member
  • Posts: 1410
  • Hero Points: 131
Re: Slickedit unusable with X forwarding
« Reply #1 on: June 02, 2008, 07:57:30 pm »
Just a guess:  I suspect that Slick-C does not use "virtual listboxes", and natively fully populates each listbox and treeview with the entire set of data.  In a virtual listbox the idea is that the listbox does not manage the list data itself, it merely manages the scrollbar and uses a callback to get the actual data as needed.  So the initialization time is almost zero, and the additional memory requirements are almost zero (or put another way, the memory cost is only 1x instead of 2x -- since the host already has the data in memory somewhere).

If SlickEdit used virtual listboxes, there are a few nasty performance issues that would probably be magically solved.  There is of course a trade-off, though, because adding virtual listbox support to Slick-C would take time, and also finding and converting the performance-problem listboxes in SlickEdit would also take time.  I'm not part of the SlickTeam, so I can't really offer a guess as to how expensive/risky/etc that might be.

But, ignoring the question of cost/risk/side effects/etc (;)), and assuming that you are right about the reason for the slowdown, then a virtual listbox implementation would probably make a difference for this particular issue.  (Again, lots of qualifiers here, because I don't know any internal details of how SlickEdit is implemented, nor even how X terminals work, though RDP terminals do not seem to suffer from this and therefore I assume that RDP sends rendered information to the client but X terminals replicate the actual windowing state to the client).

matt.newby

  • Community Member
  • Posts: 10
  • Hero Points: 0
Re: Slickedit unusable with X forwarding
« Reply #2 on: June 10, 2008, 10:19:25 pm »
One suggestion for a workaround, we use VNC to access our Linux lab from windows machines. This is a very workable solution and would almost certainly work with your network performance.  I use Slickedit and have no performance problems with this configuration.

We tried remote X  servers and had a number of problems that went away once VNC was installed, although at that time I had yet to convince the team lead that Slickedit was a valuable investment, so never came across your issue. 

pvonkaenel

  • Senior Community Member
  • Posts: 211
  • Hero Points: 6
Re: Slickedit unusable with X forwarding
« Reply #3 on: April 06, 2015, 06:20:33 pm »
This topic is very old at this point, and while I do not see the excessive lag times described here, I do find the editor to be unusably slow when run in a remote X session.  I have an i7-4770 running CentOS 7, and a MacBook Pro 13" (late 2013) - both fairly current machine that run quite fast.  When I ssh into CentOS from OSX, I am able to start VS 19.0.1.1 within a few seconds in a X session (in XQuartx 2.7.7).  However moving the mouse cursor from the keyboard or even double clicking on a word to highlight it is very slow.

Does anyone have a suggestion on how to get better performance from a remote VS X, or is the current suggestion to still use VLC?  This really is not preferred, but I'll do it if I have to.  I will gladly turn off editor features or change X session parameters if that will help.

Thanks,
Peter

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 6468
  • Hero Points: 504
Re: Slickedit unusable with X forwarding
« Reply #4 on: April 06, 2015, 11:12:46 pm »
Try using the "-graphicssystem native" invocation option. It could help but only if SlickEdit was unable to auto detect the graphics system.

pvonkaenel

  • Senior Community Member
  • Posts: 211
  • Hero Points: 6
Re: Slickedit unusable with X forwarding
« Reply #5 on: April 07, 2015, 11:25:01 am »
I tried it from home last night through the VPN, and it took a couple  of minutes before VS was ready to use.  Even then I could only move the mouse cursor with the keyboard at about a character every 5 seconds.

However, now that I'm back in the office and all local, the speed is improved.  I think I'll be able to use X forwarding in the office, and use VNC from home.

Thanks for the tip,
Peter

Phil Barila

  • Senior Community Member
  • Posts: 742
  • Hero Points: 61
Re: Slickedit unusable with X forwarding
« Reply #6 on: April 08, 2015, 02:12:43 pm »
I think the problem is that X just really stinks over VPNs.  I've seen the same abysmal performance over X forwarding with Eclipse.  It's so bad that I use a Windows X host and RDP that over the VPN, which is about the same perf as VNC.

gskerl

  • New Community Member
  • Posts: 1
  • Hero Points: 1
Re: Slickedit unusable with X forwarding
« Reply #7 on: June 25, 2015, 10:31:25 pm »
I just stumbled on to something that might help.  I'm using Slickedit 17.0.3 and noticed that when the "current line" is visible (and nothing else happening), Slickedit uses about 300 Kb/s of network bandwidth.  After some trial and error, I found that if I set "Tools->Options->Appearance->General->Current Line Highlight" to "None", then the network usage decreases to about 50 Kb/s.

As a workaround for the current line highlight, I found that I could go to "Tools->Options->Appearance->Colors->Current Line" and set the background color to something similar to, but different than the normal background, it works perfectly as a current line highlight without killing my network.

pvonkaenel

  • Senior Community Member
  • Posts: 211
  • Hero Points: 6
Re: Slickedit unusable with X forwarding
« Reply #8 on: June 30, 2015, 01:39:56 pm »
Wow, thanks for the trick.  I have not tried it through the VPN yet, but it has already fixed another problem where intellisense was not coming up in my X session.

+1

Peter

florihupf

  • Community Member
  • Posts: 30
  • Hero Points: 0
Re: Slickedit unusable with X forwarding
« Reply #9 on: April 29, 2020, 02:58:12 pm »
Just a super quick thank you to Clark!

Using vs -graphicssystem native makes it run SOOOOOOOO MUCHHHHHH FASTER over x2go.

So cheers!