[JBoss JIRA] Created: (JBIDE-2173) Performance problems with rather big db - Hibernate Console view can't process rather big amount of tables
by Vitali Yemialyanchyk (JIRA)
Performance problems with rather big db - Hibernate Console view can't process rather big amount of tables
----------------------------------------------------------------------------------------------------------
Key: JBIDE-2173
URL: http://jira.jboss.com/jira/browse/JBIDE-2173
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Hibernate
Reporter: Vitali Yemialyanchyk
Assigned To: Vitali Yemialyanchyk
Priority: Minor
For test purposes I create org.hibernate.eclipse.console.test -> org.hibernate.eclipse.console.db.test.BigDBCreateTest - the main goal of this class is creation test database with specified number of related tables. Then with help of BigDBCreateTest I create a big enough databases with different number of tables in it. And then I try to test hibernate plugins performance. I create a configuration for my test db.
In Hibernate Console I try to expand tree. Here is a time:
200 tables in db - takes 40 seconds;
300 tables in db - takes 2 minutes 45 seconds;
500 tables in db - too long I do not get results.
Remark: I use MySQL as test db. 3000 tables - too much for MySQL. Also - it is intresting - when I create such big db - I try to expand Hibernate Console tree - I get MySQL exception - but in this case Hibernate Console display all items quickly!
JBIDE-2162 is related;
JBIDE-2163 & JBIDE-2164 are related by implication - till the moment when I have fixed its in my test environment - I can't see performance problems.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (JBIDE-12144) EGitUtils#push is throwing an exception if push fails. It should not and use the same semantics as EGit
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-12144:
----------------------------------------
Summary: EGitUtils#push is throwing an exception if push fails. It should not and use the same semantics as EGit
Key: JBIDE-12144
URL: https://issues.jboss.org/browse/JBIDE-12144
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 3.3.0.CR1
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 3.3.x, 3.4.x
EgitUtils#push throws an exception if the push failed because of ex. "non fastforward push".
{code}
private static PushOperationResult push(Repository repository, RemoteConfig remoteConfig,
boolean force, IProgressMonitor monitor) throws CoreException {
...
PushOperationResult pushResult = op.getOperationResult();
if (hasFailedEntries(pushResult)) {
throw new CoreException(
EGitCoreActivator.createErrorStatus(
NLS.bind("Could not push repository {0}: {1}",
repository.toString(), getErrors(pushResult))
, null));
}
return pushResult;
{code}
EGit is not throwing an exception in this case. You simply get the failure in the PushResult object you'll have to look at.
EGitUtils#push is thus changing the API semantics of EGit and it shouldn't.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months