How long we prefer to clear transaction for not make Samba POS become slow?
Years and years, if your using full sql it shouldnt slow for a very long time
I remember a previous conversation where samba had been tested with a few hundred thousand tickets and there wasno effect on speed
I use AIO Asus with celeron processor, and 2 GB ram. and now have rich 10,000 transaction record. perfomance just slow at begining create order, and at finish settle payment. and a little slow at show table amount and entity state time. I ask for prepare what should best to make Samba Fast again because minimum spec my computer. Not Samba Pos is slow.
Are you using SQL or CE? You should never delete data.
i use Sql Sever 2014 for database
SQL Server can handle an immense amount of data before it would slow down.
People on the forum have been using samba for many years in very busy businesses without issue.
Are you experiencing slow system?
Your computer may be on the lite side, is it a single terminal system or do you have multiple terminals?
I would at least upgrade to 4GB of RAM and an SSD however Processor itself is older/lowend Celeron.
My basic system I sell is a Late Core2Duo 3Ghz with 4GB RAM and 500/500MBs SSD
You can put together a SFF PC with these specs or better for not a huge amount of money.
Is that one of those all in one touch screen desktop machines?
If upgrading its specs is dificult you could eleiviate with the above SFF PC setup as a SQL ‘server’ and just have the Asus as a client with Samba reading from the server.
RAM and SSD wouldnt go a miss either way.
i use asus et1612 all in one desktop spec, ram 2GB, still use HDD.
Windows run normal, no slow.
just as single terminal.
it slow just for first create order, after that it normal. and slow agian after close payment.
and slow ata entity screen table. i show total amount, time order at table screen.
Pretty sure 2GB is min recommendation for windows 7 - at least for 64bit, thats why I say 4GB preferred.
Also SQL does allot of reads and writes which is why an SSD offered improved performance not just for windows but also SQL.
In mean time check if you have any complex rules on those events which might be causing the lag at those points.
If you are using SQL it will be either or combination of configuration or pc spec as SQL would not be a limiting factor at least untill you have millions of transactions.
oke. now, i can’t change RAM and SSD because warranty.
Yes, i have more check rule at these point.
OK, so how long have you been running samba to be getting sluggishness you expect is due to large database?
i use Samba From Nov 2015, until now may be 7 month, samba get a little slow at some point this 3 month.
Seriously doubt this is anything to do with database size… 7 months is not allot especially on a single terminal.
Largest setup ive done is 5 terminals in 1200 capacity club just over a year ago and not had any issues there.
May be because minimum spec of AIO Desktop. Because, when i try at my notebook with core i3 and 4 GB, i didn’t get problem
Is this running SQL on the laptop?
Try running the ASUS via network to the laptop SQL.
That would simulate you buying a repetitively cheap better spec SFF PC as a ‘server’ for the SQL and just using the ASUS as a client terminal.
Yes, at my laptop i running SQL, with backup database, and not connect to Live transaction at AIO Desktop.
Thats what im saying… during closed hours change the database connection string (remember/save the existing one so can put back after test) so that the Asus is connecting via the network to the laptop SQL.
If this helps you will be able to get a SFF PC with better spec than Asus, probably dont need as good as the laptop, and use that as an SQL ‘server’.
If the specs of the Asus are sufficient to just be a client machine that will probably be the next best option if upgrading the Asus specs is not an option.
Something like this for example…
http://www.ebay.co.uk/itm/Dell-Optiplex-790-SFF-Core-i3-2120-3-30GHz-4GB-250GB-DVD-ROM-WIN-7-PRO-64bit-/201583056627?hash=item2eef4956f3:g:vuAAAOSwoudW69IG
Have that out the way in the office on the network and the asus could run of the SQL ‘hosted’ by that machine so that the Asus doesnt have to run everything.
Also means you wont need to worry should you ever want to add a tablet or second terminal which would likely make things even worse if trying to run from the Asus