[KonyanHau]

I am using Win7 64 bits OS, and was used MobiOne_2.5.0M1-M3 to develop & test my apps with no problem, but when I upgrade to MobiOne_2.5.0 production release I have encountered loading Designer Center and testing in Test Center very very slow.

I have resintalled & activated several times and noticed that after I actiavted MobiOne with my unlock key, Mobione become very very very slow.

Listed below is Mobione log:
!SESSION 2013-11-09 22:28:42.634 ———————————————–
eclipse.buildId=unknown
java.version=1.6.0_12
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=zh_CN
Command-line arguments: -os win32 -ws win32 -arch x86

!ENTRY com.genuitec.mobione.designer 1 0 2013-11-09 22:28:45.660
!MESSAGE No recentfile.xml history file found

!ENTRY com.genuitec.mobione.update 1 0 2013-11-09 22:30:36.021
!MESSAGE Check for updates: OK

!ENTRY com.genuitec.mobione.developer 1 0 2013-11-09 22:30:38.642
!MESSAGE Unable to load recent files registry: C:\Users\rhau\.mobione\runtime\filesToUUIDs.xml

!ENTRY org.eclipse.core.filesystem 1 1 2013-11-09 22:34:06.416
!MESSAGE Could not load library: localfile_1_0_0.dll. This library provides platform-specific optimizations for certain file system operations. This library is not present on all platforms, so this may not be an error. The resources plug-in will safely fall back to using java.io.File functionality.
!STACK 0
java.lang.UnsatisfiedLinkError: no localfile_1_0_0 in java.library.path
at java.lang.ClassLoader.loadLibrary(Unknown Source)
at java.lang.Runtime.loadLibrary0(Unknown Source)
at java.lang.System.loadLibrary(Unknown Source)
at org.eclipse.core.internal.filesystem.local.LocalFileNatives.<clinit>(LocalFileNatives.java:32)
at org.eclipse.core.internal.filesystem.local.LocalFile.fetchInfo(LocalFile.java:143)
at org.eclipse.core.filesystem.provider.FileStore.fetchInfo(FileStore.java:277)
at com.genuitec.eclipse.dehory.fs.DehoryEfsFile.exists(DehoryEfsFile.java:49)
at com.genuitec.eclipse.dehory.fs.DehoryEditorFileStorage.formFileExists(DehoryEditorFileStorage.java:58)
at com.genuitec.eclipse.dehory.fs.DehoryInput.formFileExists(DehoryInput.java:87)
at com.genuitec.eclipse.dehory.DehoryEditor.init(DehoryEditor.java:219)
at org.eclipse.ui.internal.EditorManager.createSite(EditorManager.java:798)
at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:644)
at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:462)
at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595)
at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:286)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2860)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2765)
at org.eclipse.ui.internal.WorkbenchPage.access$11(WorkbenchPage.java:2757)
at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2708)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2704)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2688)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2671)
at org.eclipse.ui.ide.IDE.openEditor(IDE.java:439)
at com.genuitec.eclipse.fileview.DefaultOpenDelegate.openFile(DefaultOpenDelegate.java:20)
at com.aptana.ide.core.ui.views.fileexplorer.FileExplorerView.openFileInEditor(FileExplorerView.java:2155)
at com.aptana.ide.core.ui.views.fileexplorer.FileExplorerView.openFileInEditor(FileExplorerView.java:2123)
at com.aptana.ide.core.ui.views.fileexplorer.FileExplorerView$12.run(FileExplorerView.java:1581)
at com.aptana.ide.core.ui.views.fileexplorer.FileExplorerView$28.doubleClick(FileExplorerView.java:2386)
at org.eclipse.jface.viewers.StructuredViewer$1.run(StructuredViewer.java:821)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.runtime.Platform.run(Platform.java:888)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
at org.eclipse.jface.viewers.StructuredViewer.fireDoubleClick(StructuredViewer.java:819)
at org.eclipse.jface.viewers.AbstractTreeViewer.handleDoubleSelect(AbstractTreeViewer.java:1419)
at org.eclipse.jface.viewers.StructuredViewer$4.widgetDefaultSelected(StructuredViewer.java:1195)
at org.eclipse.jface.util.OpenStrategy.fireDefaultSelectionEvent(OpenStrategy.java:238)
at org.eclipse.jface.util.OpenStrategy.access$0(OpenStrategy.java:235)
at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:296)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3910)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3503)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at com.genuitec.mobione.developer.rcp.MobiOneApplication.start(MobiOneApplication.java:461)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)

[support-octavio]

Hi richardhau,

Could you share details about your environment? (Windows version, RAM installed, if you run other apps at the same time you’re running mobione).

Could you please attach your complete .log file?

[KonyanHau]

Hi octavio,

Just return from trip, I am using Windows 7 64-bits Ultimate with 4 GB ram on my Acer I5 notebook.

Normally I will have VS2010 and Outllook 2007 running with MB1, please check what cause this problem.

Thanks,
Richard Hau

Attachments:

You must be logged in to view attached files.

[support-michael]

>please check what cause this problem.

Please quantify what “slow” means on your system?

MobiOne 2.5 includes additional editors which can be a little slow to load initially. But after starting the first editor (e.g., html or js editor) it should be perform quickly. On our system we see 2-5 seconds on the initial loading of the javascript editor. If you are not using any editor other than the Visual Designer startup performance should be close to that of earlier versions of MobiOne.

Also there is new mobile web simulator (not the old test center – it is deprecated) can take a few seconds to initially load. There is some overhead of setting up the infrastructure and instrumenting the app to run and support auto-reload. Again performance should improve after the 1st use of the simulator as the services are already running.

We are evaluating areas of optimization now. Your feedback on where processes and actions are slow will be appreciated.

[KonyanHau]

Hi wayne,

This test is done on MB1 V2.5 after key activation, it takes 2.30 minutes to load designer, and takes over 5 minutes on starting Mobile Web Simulator. Most of the time are in Generating layout, CSS, Javascript, minimizing javascript code.

I have reinstall a fresh MB1 V2.5 without activate my key on the same environment, it takes 10 seconds to load designer, and takes 5 seconds to start Mobile Web Simulator.

Enclosed please find the .log on the test without activation.

Regards,
Richard Hau

Attachments:

You must be logged in to view attached files.

[support-michael]

Richard,
Thx for the log. The performance info you shared is definitely atypical for mobione. Also the performance diff of reinstalled version. I can not intuit the performance diff just yet. Thinking…

Questions:
1) if you activate mobione does the performance drop off?
1a) if yes, then try disabling the Windows menu>Setting>Software Updates “Automatically check for Updates” setting and restart. Does performance improve?

2) if your reboot machine and then run only mobione, what is performance experience?
2a) how does performance degrade if you systematically start other common programs (outlook, vs) one at a time and test mobione use-cases between each program launch?

[KonyanHau]

Hi wayne,

1) if you activate mobione does the performance drop off?
1a) if yes, then try disabling the Windows menu>Setting>Software Updates “Automatically check for Updates” setting and restart. Does performance improve?
– I have disable the “Automatically check for Updates”, but no improvement.

2) if your reboot machine and then run only mobione, what is performance experience?
2a) how does performance degrade if you systematically start other common programs (outlook, vs) one at a time and test mobione use-cases between each program launch?
– I have reboot my notebook and run only mobione, no performance improve.

[support-octavio]

Hi richardhau,

Could you try running M1 with network disabled?

If the problem continues, also please try uninstalling Mobione and then clean .mobione dir from <userhome>\.mobione.

Let us know how it goes.

[KonyanHau]

Hi octavio,

I have tried to disable all my networks, still not work.

I have also unistalled mobione many times and .mobile directory still not work.

Regards,
Richard Hau

[support-michael]

Hi Richard,

We have not forgotten of this issue.

>I have reinstall a fresh MB1 V2.5 without activate my key on the same environment, it takes 10 seconds to load designer, and takes 5 seconds to start Mobile Web Simulator.

Summarizing what we know (please correct any misunderstandings):
1. pre-activation performance is quick
2. post-activation performance is dramatically slower
3. you indicated that code generation seems to be the bottleneck
4. disabling network activities such as check for updates had no improvement

Thoughts, I’m perplexed by #1 & #2 differences. I’m wondering if it is a red herring.

Actions to try to isolate the problem:
1. choose Tools menu>Mobile Web Simulator to launch the Simulator with no code generation activities. Does the Simulator launch more quickly
2. next, create a new design file (.mobi) with no widgets on it and save it to a local non-shared directory. Set the Target Design (on toolbar) to <Current .mobi editor>. Then choose Project menus>Generate Application Files. How is the performance

[KonyanHau]

Hi wayne,

Case 1. Just launch Mobile Web Simulator from Tools menu, it launched very quick
Case 2. Generate Application Files from the Project menu, the performance is bad, like before.

Regards,
Richard Hau

[support-michael]

> Case 2. Generate Application Files from the Project menu, the performance is bad, like before.

Thanks for this info. Kicking it to the dev team for analysis.

[Author]

Posts