I think it may have something to do with the processor. The sytem is running an atom processor that shoots up to 96-100% usage whenever the cash closed button is pressed. I'm having to exit to desktop then launch unicenta again, then press close cash without ringing in any transactions. Even then it still takes a good minute to work.
Trying the database on another sytem with a better processor seems to sort it out. It works in seconds.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So, what does that tell you? You're under-powered. Yes?
And, you're using default Apache Derby Embedded, right?
You should read the "advisory" in the Configuration panel and act accordingly on that.
As an aside: change the start.bat by adding something like -Xms256m and -Xmx512m to the javaw start line command.
Jack
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi
When I want to cash up or see the takings so far, after pressing the Close cash button the screen takes a long time to load.
Thanks
Robert
We are experiencing this on 3.6 any shed any light stand alone pc using derby database.
Thanks Colin
fanzam, neeed u'r help really appriciate if u can give me som help... thanxs before ^^ https://sourceforge.net/p/unicentaopos/discussion/1126901/thread/5e68add4/
I think it may have something to do with the processor. The sytem is running an atom processor that shoots up to 96-100% usage whenever the cash closed button is pressed. I'm having to exit to desktop then launch unicenta again, then press close cash without ringing in any transactions. Even then it still takes a good minute to work.
Trying the database on another sytem with a better processor seems to sort it out. It works in seconds.
robert
So, what does that tell you? You're under-powered. Yes?
And, you're using default Apache Derby Embedded, right?
You should read the "advisory" in the Configuration panel and act accordingly on that.
As an aside: change the start.bat by adding something like -Xms256m and -Xmx512m to the javaw start line command.
Jack