English Amiga Board


Go Back   English Amiga Board > Support > support.Other

 
 
Thread Tools
Old 22 July 2023, 12:26   #21
Solskogen
Registered User
 
Join Date: Nov 2016
Location: Skien / Norway
Posts: 111
Disk speed on a 128GB hdf on the MiSTER fpga with 512 block size:

MKSoft DiskSpeed 4.2 Copyright © 1989-92 MKSoft Development
------------------------------------------------------------
CPU: 68020 AmigaOS Version: 47.111 Normal Video DMA
Device: dh1: Buffers: 150
Comments: DiskSpeed 4.2

CPU Speed Rating: 1765

Testing directory manipulation speed.
File Create: 445 files/sec | CPU Available: 0%
File Open: 586 files/sec | CPU Available: 0%
Directory Scan: 3814 files/sec | CPU Available: 0%
File Delete: 547 files/sec | CPU Available: 0%

Seek/Read: 1416 seeks/sec | CPU Available: 30%

Testing with a 512 byte, MEMF_FAST, LONG-aligned buffer.
Create file: 622453 bytes/sec | CPU Available: 37%
Write to file: 793344 bytes/sec | CPU Available: 39%
Read from file: 617728 bytes/sec | CPU Available: 12%

Testing with a 4096 byte, MEMF_FAST, LONG-aligned buffer.
Create file: 722041 bytes/sec | CPU Available: 65%
Write to file: 777728 bytes/sec | CPU Available: 67%
Read from file: 1510400 bytes/sec | CPU Available: 50%

Testing with a 32768 byte, MEMF_FAST, LONG-aligned buffer.
Create file: 1405510 bytes/sec | CPU Available: 75%
Write to file: 1577113 bytes/sec | CPU Available: 77%
Read from file: 3452928 bytes/sec | CPU Available: 25%

Testing with a 262144 byte, MEMF_FAST, LONG-aligned buffer.
Create file: 1405510 bytes/sec | CPU Available: 78%
Write to file: 1591704 bytes/sec | CPU Available: 79%
Read from file: 4564696 bytes/sec | CPU Available: 6%

Testing with a 512 byte, MEMF_FAST, WORD-aligned buffer.
Create file: 656906 bytes/sec | CPU Available: 35%
Write to file: 799040 bytes/sec | CPU Available: 40%
Read from file: 566272 bytes/sec | CPU Available: 19%

Testing with a 4096 byte, MEMF_FAST, WORD-aligned buffer.
Create file: 715776 bytes/sec | CPU Available: 65%
Write to file: 772608 bytes/sec | CPU Available: 67%
Read from file: 1506816 bytes/sec | CPU Available: 50%

Testing with a 32768 byte, MEMF_FAST, WORD-aligned buffer.
Create file: 1390901 bytes/sec | CPU Available: 75%
Write to file: 1583173 bytes/sec | CPU Available: 77%
Read from file: 3448402 bytes/sec | CPU Available: 25%

Testing with a 262144 byte, MEMF_FAST, WORD-aligned buffer.
Create file: 1259066 bytes/sec | CPU Available: 71%
Write to file: 1620173 bytes/sec | CPU Available: 80%
Read from file: 4532091 bytes/sec | CPU Available: 7%

Testing with a 512 byte, MEMF_FAST, BYTE-aligned buffer.
Create file: 550336 bytes/sec | CPU Available: 27%
Write to file: 617148 bytes/sec | CPU Available: 32%
Read from file: 512384 bytes/sec | CPU Available: 9%

Testing with a 4096 byte, MEMF_FAST, BYTE-aligned buffer.
Create file: 632832 bytes/sec | CPU Available: 58%
Write to file: 667136 bytes/sec | CPU Available: 59%
Read from file: 1223168 bytes/sec | CPU Available: 23%

Testing with a 32768 byte, MEMF_FAST, BYTE-aligned buffer.
Create file: 927473 bytes/sec | CPU Available: 57%
Write to file: 1086818 bytes/sec | CPU Available: 53%
Read from file: 1822720 bytes/sec | CPU Available: 9%

Testing with a 262144 byte, MEMF_FAST, BYTE-aligned buffer.
Create file: 998337 bytes/sec | CPU Available: 56%
Write to file: 1104448 bytes/sec | CPU Available: 55%
Read from file: 2024025 bytes/sec | CPU Available: 2%

Testing with a 512 byte, MEMF_CHIP, LONG-aligned buffer.
Create file: 673973 bytes/sec | CPU Available: 34%
Write to file: 805888 bytes/sec | CPU Available: 40%
Read from file: 581184 bytes/sec | CPU Available: 14%

Testing with a 4096 byte, MEMF_CHIP, LONG-aligned buffer.
Create file: 735232 bytes/sec | CPU Available: 67%
Write to file: 797696 bytes/sec | CPU Available: 69%
Read from file: 1540608 bytes/sec | CPU Available: 48%

Testing with a 32768 byte, MEMF_CHIP, LONG-aligned buffer.
Create file: 1417767 bytes/sec | CPU Available: 76%
Write to file: 1603627 bytes/sec | CPU Available: 78%
Read from file: 3387392 bytes/sec | CPU Available: 26%

Testing with a 262144 byte, MEMF_CHIP, LONG-aligned buffer.
Create file: 1418737 bytes/sec | CPU Available: 79%
Write to file: 1620173 bytes/sec | CPU Available: 80%
Read from file: 4597301 bytes/sec | CPU Available: 5%

Testing with a 512 byte, MEMF_CHIP, WORD-aligned buffer.
Create file: 634790 bytes/sec | CPU Available: 38%
Write to file: 807872 bytes/sec | CPU Available: 40%
Read from file: 556928 bytes/sec | CPU Available: 18%

Testing with a 4096 byte, MEMF_CHIP, WORD-aligned buffer.
Create file: 763904 bytes/sec | CPU Available: 56%
Write to file: 952832 bytes/sec | CPU Available: 63%
Read from file: 1664512 bytes/sec | CPU Available: 44%

Testing with a 32768 byte, MEMF_CHIP, WORD-aligned buffer.
Create file: 1528083 bytes/sec | CPU Available: 74%
Write to file: 1607718 bytes/sec | CPU Available: 78%
Read from file: 3289088 bytes/sec | CPU Available: 28%

Testing with a 262144 byte, MEMF_CHIP, WORD-aligned buffer.
Create file: 1429285 bytes/sec | CPU Available: 78%
Write to file: 1640410 bytes/sec | CPU Available: 80%
Read from file: 4478020 bytes/sec | CPU Available: 8%

Testing with a 512 byte, MEMF_CHIP, BYTE-aligned buffer.
Create file: 545685 bytes/sec | CPU Available: 29%
Write to file: 629549 bytes/sec | CPU Available: 31%
Read from file: 503552 bytes/sec | CPU Available: 10%

Testing with a 4096 byte, MEMF_CHIP, BYTE-aligned buffer.
Create file: 664064 bytes/sec | CPU Available: 58%
Write to file: 695296 bytes/sec | CPU Available: 60%
Read from file: 1131520 bytes/sec | CPU Available: 29%

Testing with a 32768 byte, MEMF_CHIP, BYTE-aligned buffer.
Create file: 1044658 bytes/sec | CPU Available: 53%
Write to file: 1107247 bytes/sec | CPU Available: 54%
Read from file: 1816353 bytes/sec | CPU Available: 9%

Testing with a 262144 byte, MEMF_CHIP, BYTE-aligned buffer.
Create file: 1015808 bytes/sec | CPU Available: 56%
Write to file: 1120273 bytes/sec | CPU Available: 54%
Read from file: 2033875 bytes/sec | CPU Available: 2%

Average CPU Available: 44% | CPU Availability index: 777
Solskogen is offline  
Old 22 July 2023, 12:35   #22
Solskogen
Registered User
 
Join Date: Nov 2016
Location: Skien / Norway
Posts: 111
Same with 4096:

MKSoft DiskSpeed 4.2 Copyright © 1989-92 MKSoft Development
------------------------------------------------------------
CPU: 68020 AmigaOS Version: 47.111 Normal Video DMA
Device: DH2: Buffers: 150
Comments: DiskSpeed 4.2

CPU Speed Rating: 1765

Testing directory manipulation speed.
File Create: 443 files/sec | CPU Available: 0%
File Open: 609 files/sec | CPU Available: 0%
Directory Scan: 3779 files/sec | CPU Available: 0%
File Delete: 507 files/sec | CPU Available: 5%

Seek/Read: 1449 seeks/sec | CPU Available: 1%

Testing with a 512 byte, MEMF_FAST, LONG-aligned buffer.
Create file: 781376 bytes/sec | CPU Available: 39%
Write to file: 596544 bytes/sec | CPU Available: 41%
Read from file: 886848 bytes/sec | CPU Available: 26%

Testing with a 4096 byte, MEMF_FAST, LONG-aligned buffer.
Create file: 1156096 bytes/sec | CPU Available: 58%
Write to file: 1274880 bytes/sec | CPU Available: 63%
Read from file: 1857536 bytes/sec | CPU Available: 17%

Testing with a 32768 byte, MEMF_FAST, LONG-aligned buffer.
Create file: 1523998 bytes/sec | CPU Available: 74%
Write to file: 1573027 bytes/sec | CPU Available: 76%
Read from file: 3452928 bytes/sec | CPU Available: 25%

Testing with a 262144 byte, MEMF_FAST, LONG-aligned buffer.
Create file: 1449199 bytes/sec | CPU Available: 79%
Write to file: 1624188 bytes/sec | CPU Available: 79%
Read from file: 4647246 bytes/sec | CPU Available: 4%

Testing with a 512 byte, MEMF_FAST, WORD-aligned buffer.
Create file: 784640 bytes/sec | CPU Available: 39%
Write to file: 580800 bytes/sec | CPU Available: 44%
Read from file: 904256 bytes/sec | CPU Available: 24%

Testing with a 4096 byte, MEMF_FAST, WORD-aligned buffer.
Create file: 1148516 bytes/sec | CPU Available: 58%
Write to file: 1269912 bytes/sec | CPU Available: 63%
Read from file: 1817600 bytes/sec | CPU Available: 19%

Testing with a 32768 byte, MEMF_FAST, WORD-aligned buffer.
Create file: 1501355 bytes/sec | CPU Available: 73%
Write to file: 1570900 bytes/sec | CPU Available: 76%
Read from file: 3080192 bytes/sec | CPU Available: 33%

Testing with a 262144 byte, MEMF_FAST, WORD-aligned buffer.
Create file: 1447420 bytes/sec | CPU Available: 79%
Write to file: 1620173 bytes/sec | CPU Available: 79%
Read from file: 4211279 bytes/sec | CPU Available: 13%

Testing with a 512 byte, MEMF_FAST, BYTE-aligned buffer.
Create file: 321119 bytes/sec | CPU Available: 16%
Write to file: 281884 bytes/sec | CPU Available: 23%
Read from file: 476104 bytes/sec | CPU Available: 11%

Testing with a 4096 byte, MEMF_FAST, BYTE-aligned buffer.
Create file: 890190 bytes/sec | CPU Available: 45%
Write to file: 930909 bytes/sec | CPU Available: 46%
Read from file: 1111552 bytes/sec | CPU Available: 18%

Testing with a 32768 byte, MEMF_FAST, BYTE-aligned buffer.
Create file: 1067721 bytes/sec | CPU Available: 52%
Write to file: 1090904 bytes/sec | CPU Available: 53%
Read from file: 1712128 bytes/sec | CPU Available: 15%

Testing with a 262144 byte, MEMF_FAST, BYTE-aligned buffer.
Create file: 1034353 bytes/sec | CPU Available: 56%
Write to file: 1114112 bytes/sec | CPU Available: 55%
Read from file: 2033875 bytes/sec | CPU Available: 2%

Testing with a 512 byte, MEMF_CHIP, LONG-aligned buffer.
Create file: 788864 bytes/sec | CPU Available: 40%
Write to file: 581696 bytes/sec | CPU Available: 44%
Read from file: 901888 bytes/sec | CPU Available: 21%

Testing with a 4096 byte, MEMF_CHIP, LONG-aligned buffer.
Create file: 1192718 bytes/sec | CPU Available: 59%
Write to file: 1327756 bytes/sec | CPU Available: 64%
Read from file: 1449984 bytes/sec | CPU Available: 30%

Testing with a 32768 byte, MEMF_CHIP, LONG-aligned buffer.
Create file: 1517718 bytes/sec | CPU Available: 74%
Write to file: 1591354 bytes/sec | CPU Available: 77%
Read from file: 3203072 bytes/sec | CPU Available: 30%

Testing with a 262144 byte, MEMF_CHIP, LONG-aligned buffer.
Create file: 1456355 bytes/sec | CPU Available: 80%
Write to file: 1630248 bytes/sec | CPU Available: 80%
Read from file: 4281903 bytes/sec | CPU Available: 12%

Testing with a 512 byte, MEMF_CHIP, WORD-aligned buffer.
Create file: 785728 bytes/sec | CPU Available: 39%
Write to file: 601664 bytes/sec | CPU Available: 42%
Read from file: 889920 bytes/sec | CPU Available: 22%

Testing with a 4096 byte, MEMF_CHIP, WORD-aligned buffer.
Create file: 1193182 bytes/sec | CPU Available: 60%
Write to file: 1325086 bytes/sec | CPU Available: 64%
Read from file: 1391616 bytes/sec | CPU Available: 33%

Testing with a 32768 byte, MEMF_CHIP, WORD-aligned buffer.
Create file: 1550445 bytes/sec | CPU Available: 75%
Write to file: 1591354 bytes/sec | CPU Available: 77%
Read from file: 3407872 bytes/sec | CPU Available: 26%

Testing with a 262144 byte, MEMF_CHIP, WORD-aligned buffer.
Create file: 1458155 bytes/sec | CPU Available: 80%
Write to file: 1634314 bytes/sec | CPU Available: 80%
Read from file: 4656719 bytes/sec | CPU Available: 4%

Testing with a 512 byte, MEMF_CHIP, BYTE-aligned buffer.
Create file: 325394 bytes/sec | CPU Available: 17%
Write to file: 285468 bytes/sec | CPU Available: 23%
Read from file: 490496 bytes/sec | CPU Available: 9%

Testing with a 4096 byte, MEMF_CHIP, BYTE-aligned buffer.
Create file: 918681 bytes/sec | CPU Available: 46%
Write to file: 959488 bytes/sec | CPU Available: 48%
Read from file: 1130496 bytes/sec | CPU Available: 17%

Testing with a 32768 byte, MEMF_CHIP, BYTE-aligned buffer.
Create file: 1059539 bytes/sec | CPU Available: 52%
Write to file: 1099076 bytes/sec | CPU Available: 53%
Read from file: 1742717 bytes/sec | CPU Available: 13%

Testing with a 262144 byte, MEMF_CHIP, BYTE-aligned buffer.
Create file: 1039480 bytes/sec | CPU Available: 57%
Write to file: 1125771 bytes/sec | CPU Available: 55%
Read from file: 1983968 bytes/sec | CPU Available: 4%

Average CPU Available: 41% | CPU Availability index: 724
Solskogen is offline  
Old 22 July 2023, 19:59   #23
Toni Wilen
WinUAE developer
 
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,518
Not sure what to say about those test results. I'd have expected some more differences. Unless MiSTER somehow splits transfers or does some processing ore maybe slow part is Amiga side and card is more than fast enough, hiding the differences.
Toni Wilen is offline  
Old 22 July 2023, 23:08   #24
TuKo
Apollo Team
 
TuKo's Avatar
 
Join Date: May 2014
Location: not far
Posts: 379
It would probably shine on a faster system than TG68, i.e. 060@100MHz or 080
TuKo is offline  
Old 23 July 2023, 19:06   #25
Toni Wilen
WinUAE developer
 
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,518
Test 4:

- Larger partition size reserved block increased yet again. (500 000+ files/directories again possible with larger partitions now)
- Implemented (forgotten because it was v39 introduced?) ACTION_EXAMINE_ALL_END. Almost no-operation packet handler function, no need to free anything. Probably does not make much difference because dos.library emulates this if it is not implemented.
- Allow file sizes up to 4G-1 (previously was 2G-1), allows smoother on the fly switch to >=4G mode if needed in the future. >=4G support mode is currently disabled.
Toni Wilen is offline  
Old 24 July 2023, 12:27   #26
pcotter
Registered User
 
Join Date: Aug 2016
Location: Germany
Posts: 122
10GB to go Toni :-)

Will try also to take some benchmarks.
Attached Thumbnails
Click image for larger version

Name:	test4.png
Views:	90
Size:	87.9 KB
ID:	79703  
pcotter is offline  
Old 24 July 2023, 16:53   #27
Toni Wilen
WinUAE developer
 
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,518
Quote:
Originally Posted by pcotter View Post
10GB to go Toni :-)

Will try also to take some benchmarks.
I am not yet sure if this is case that does not happen in real world. It probably does but I'll think about it first

If you do any comparisons (512 vs 4096), could you also check free RAM size difference when booted without startup-sequence?

Filesystem benchmarks in UAE are not that useful as I already said previously. Host OS HD cache can "hide" the difference. CF/SD card in USB reader mounted in WinUAE as a full Amiga drive might make a difference because in this case host OS cache gets bypassed.
Toni Wilen is offline  
Old 25 July 2023, 23:37   #28
janz
Registered User
 
Join Date: Dec 2019
Location: EU
Posts: 12
For some reason I cannot format the microSD card using WinUAE running in admin mode. It gets stuck at "Initializing disk" even when run without s-s.

HDToolbox: File System PFS\03
Mask: 0x7FFFFFFE
MaxTransfer: 0x0001FE00
File System Block Size: 4096
Identifier: 0x50465303
Version: 20.0
Buffers: 500
Partition Size: 7.9G
PBS=512, LBS=4096, RBS=4096

Command: pfsformat device=ak0_0: name=AK QUICK
janz is offline  
Old 26 July 2023, 00:03   #29
janz
Registered User
 
Join Date: Dec 2019
Location: EU
Posts: 12
It seems my card reader died. Please ignore my previous report. I will try with a new card reader later.
janz is offline  
Old 26 July 2023, 09:49   #30
janz
Registered User
 
Join Date: Dec 2019
Location: EU
Posts: 12
A speedtest using WinUAE 5.0.0 (32bit) on Windows 10, copying of 44588 files (974894626 bytes) from a SFS 1.280 hardfile with a filesystem block size of 1024 to a 7.9GB partition of a 32GB Sandisk Ultra microSDHC (120MB/S) card using a USB-C card reader:

PFS 0.19 with a filesystem block size of 512: 341 seconds

PFS 0.20t4 with a filesystem block size of 4096: 199 seconds

(max file size = default)

Btw. after formatting with PFS 0.20t4 the Trashcan folder could not be deleted (object in use). I had to reboot to delete it. This did not happen with PFS 0.19.


For comparison:

SFS 1.280 with a filesystem block size of 512: 414 seconds

SFS 1.280 with a filesystem block size of 4096: 250 seconds

I will send you the pfsdoctor outputs by email.
janz is offline  
Old 26 July 2023, 12:52   #31
Toni Wilen
WinUAE developer
 
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,518
That looks much better and thanks for including other FS results too because it shows also similar 512 vs 4096 difference, confirming difference is block size, not some filesystem difference.

Quote:
Btw. after formatting with PFS 0.20t4 the Trashcan folder could not be deleted (object in use). I had to reboot to delete it. This did not happen with PFS 0.19.
Did you do everything 100% identically? Perhaps WB or some 3rd party utility locked it when doing some WB operation or it does it periodically. Trashcan is just directory like any other directory from FS point of view.
Toni Wilen is offline  
Old 27 July 2023, 09:31   #32
TuKo
Apollo Team
 
TuKo's Avatar
 
Join Date: May 2014
Location: not far
Posts: 379
Giving a try to test4, I found a different behaviour than on 19.2 : I do keep LZX archives of my boot partition, including some empty folders. Unarchiving them on 19.2 goes without trouble and no error. With 20.0, LZX warns me about potential "disk full" error.
TuKo is offline  
Old 27 July 2023, 10:05   #33
janz
Registered User
 
Join Date: Dec 2019
Location: EU
Posts: 12
Quote:
Originally Posted by Toni Wilen View Post
That looks much better and thanks for including other FS results too because it shows also similar 512 vs 4096 difference, confirming difference is block size, not some filesystem difference.


Did you do everything 100% identically? Perhaps WB or some 3rd party utility locked it when doing some WB operation or it does it periodically. Trashcan is just directory like any other directory from FS point of view.

The Trashcan being an "object in use" issue happens in both .19 and .20 filesystems. False alarm, sorry about that.
janz is offline  
Old 27 July 2023, 10:07   #34
janz
Registered User
 
Join Date: Dec 2019
Location: EU
Posts: 12
Quote:
Originally Posted by TuKo View Post
Giving a try to test4, I found a different behaviour than on 19.2 : I do keep LZX archives of my boot partition, including some empty folders. Unarchiving them on 19.2 goes without trouble and no error. With 20.0, LZX warns me about potential "disk full" error.
This is a known behaviour of LZX on any filesystem, a harmless bug when unpacking empty directories. The empty directories get unpacked in the end, but with this inappropriate "disk full" comment.
janz is offline  
Old 28 July 2023, 07:36   #35
pcotter
Registered User
 
Join Date: Aug 2016
Location: Germany
Posts: 122
Which MaxTrasfer should we use Toni?
Files are getting corrupted with the default MaxTrasfer values
Attached Thumbnails
Click image for larger version

Name:	maxtransfer.png
Views:	91
Size:	106.0 KB
ID:	79742   Click image for larger version

Name:	maxtransfer1.png
Views:	75
Size:	247.4 KB
ID:	79744  

Last edited by pcotter; 28 July 2023 at 07:41.
pcotter is offline  
Old 28 July 2023, 10:36   #36
Toni Wilen
WinUAE developer
 
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,518
This sounds serious and most likely nothing to do with maxtransfer but some bug in pfs3 v20.

Better not use it until I have debugged this more. Does it only happen if blocksize is >512? Or only if >1024?
Toni Wilen is offline  
Old 28 July 2023, 10:54   #37
pcotter
Registered User
 
Join Date: Aug 2016
Location: Germany
Posts: 122
Happens with >1024

Last edited by pcotter; 28 July 2023 at 16:12.
pcotter is offline  
Old 28 July 2023, 18:50   #38
Toni Wilen
WinUAE developer
 
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,518
Ahh, I didn't notice both screenshots have Direct SCSI enabled. Right, Direct SCSI mode does have wrong block size calculation in split transfers. (Introduced when >512 block size support was added)

Does it work correctly if you don't force DS? (dostype=PFS\3, not PDS\3)
Toni Wilen is offline  
Old 28 July 2023, 20:26   #39
pcotter
Registered User
 
Join Date: Aug 2016
Location: Germany
Posts: 122
Yes sir, it works :-)
Attached Thumbnails
Click image for larger version

Name:	pfs3.png
Views:	68
Size:	106.6 KB
ID:	79755  
pcotter is offline  
Old 29 July 2023, 08:53   #40
Toni Wilen
WinUAE developer
 
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,518
Test 5:

- Fixed DirectSCSI mode. DirectSCSI didn't work correctly and caused corruption if >512 block size. Pfsdoctor DirectSCSI mode was also broken.
- If for some reason max transfer is smaller than block size: return error instead of hanging in infinite loop.
- Reserved block allocation increased again.
Toni Wilen is offline  
 


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools

Similar Threads
Thread Thread Starter Forum Replies Last Post
PFS3AIO v3.1 Final Toni Wilen News 501 22 September 2023 21:55
Pfs3aio caver99 support.Apps 10 15 February 2022 19:03
Req: '240p Test Suite' similar test software for Amiga? c0dehunter support.Hardware 10 22 February 2021 21:38
Pfs3aio ???? stingray76 support.Hardware 2 19 February 2014 09:15
CD32 Frog Feast test available. Test out the final! cdoty News 42 01 April 2008 16:20

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +2. The time now is 23:57.

Top

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.
Page generated in 0.09794 seconds with 14 queries